Security readout for executives and security teams
A vulnerable Spring Cloud Gateway app can let an unauthenticated remote attacker run code on the server if the Gateway Actuator endpoint is enabled, exposed, and unsecured. This is business-critical because gateway services often sit on traffic paths and can expose secrets, internal systems, and customer-facing availability. Exposure is most likely in Java services using Spring Cloud Gateway 3.1.x before 3.1.1, 3.0.x before 3.0.7, or unsupported older versions, where the Gateway Actuator endpoint is enabled, reachable, and not properly secured. Treat this as urgent for any internet-reachable or broadly reachable gateway service. Prioritize patching and actuator exposure review before routine backlog work, because the flaw is critical, remotely reachable under common misconfiguration conditions, and listed by CISA as known exploited. Mitigation focus: Upgrade Spring Cloud Gateway to 3.1.1+, 3.0.7+, or a currently supported fixed release.; Disable the Gateway Actuator endpoint if it is not operationally required.; Restrict actuator access to trusted management networks only..
Michael Williams reviewed this cited source version on .
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 lookupCVE-2022-22947 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
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
CISA KEV status
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:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://tanzu.vmware.com/security/cve-2022-22947CVE reference
- https://www.oracle.com/security-alerts/cpuapr2022.htmlCVE reference
- https://www.oracle.com/security-alerts/cpujul2022.htmlCVE reference
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-22947CVE reference · government-resource
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.