Security readout for executives and security teams
Plain-English summary
This vulnerability affects an AsyncAPI code-generation template, not a typical exposed web endpoint. If an attacker can control the AsyncAPI document used by vulnerable versions before 0.7.0, they may inject arbitrary code into the generated Spring Cloud Stream microservice. The vendor states there are no mitigations and users should update.
Executive priority
Treat this as a high-priority supply-chain and build-pipeline issue if your teams generate services from AsyncAPI documents. Runtime exposure depends on how generated code was produced, so prioritize inventory, upgrade, and review of untrusted generation inputs.
Technical view
@asyncapi/java-spring-cloud-stream-template before 0.7.0 is vulnerable to CWE-94 code injection when processing attacker-controlled AsyncAPI documents. CVSS 3.1 is 8.7: network attack vector, low complexity, high privileges required, no user interaction, changed scope, high confidentiality and integrity impact, no availability impact.
Likely exposure
Exposure is most likely in development or CI/CD workflows that use this template to generate Spring Cloud Stream services from AsyncAPI documents, especially documents supplied by external parties or less-trusted repositories.
Exploitation context
The provided sources do not report active exploitation, and CISA KEV is false. Exploitation requires attacker control over the AsyncAPI document and, per CVSS, high privileges. The advisory references an example, but this analysis does not include exploit details.
Researcher notes
Evidence is limited to CVE metadata and the GitHub advisory. The issue is code injection in a generator template before 0.7.0, triggered by attacker-controlled AsyncAPI content. No public source in the bundle confirms exploitation in the wild.
Mitigation direction
- Update @asyncapi/java-spring-cloud-stream-template to version 0.7.0 or later.
- Do not rely on compensating mitigations; sources state none are available.
- Restrict generation workflows to trusted AsyncAPI documents until updated.
- Review vendor advisory before accepting external AsyncAPI specifications.
Validation and detection
- Inventory package manifests and lockfiles for template versions before 0.7.0.
- Check CI/CD jobs and developer scripts that invoke AsyncAPI generation.
- Identify whether any generated services used externally supplied AsyncAPI documents.
- Confirm dependency inventory shows version 0.7.0 or later after remediation.
- Review generated code from untrusted inputs for unexpected code changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-37694 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N2.35.8Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.7HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/asyncapi/java-spring-cloud-stream-template/security/advisories/GHSA-xj6r-2jpm-qvxpCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.