Security readout for executives and security teams
Spring4Shell is a critical remote code execution flaw in Spring Framework applications. The common confirmed scenario is Spring MVC or WebFlux on JDK 9+, deployed to Tomcat as a WAR. CISA lists it as known exploited, so internet-facing Java applications deserve urgent review. Highest exposure is public Spring MVC or WebFlux applications running on JDK 9+ with vulnerable Spring versions and Tomcat WAR deployment. Spring Boot executable jar deployments are stated as not vulnerable to the known exploit path, but unsupported Spring versions still require review. Treat as urgent for any organization running Java web applications. Known exploitation and unauthenticated remote code execution potential justify immediate inventory and remediation, especially for internet-facing Spring applications and vendor appliances that bundle Spring. Mitigation focus: Upgrade Spring Framework to 5.3.18+, 5.2.20+, or a supported later release.; Inventory all Spring MVC and WebFlux applications, including embedded and vendor-managed products.; Prioritize internet-facing Tomcat WAR deployments running on JDK 9 or later..
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 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-2022-22965 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
- 9.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://tanzu.vmware.com/security/cve-2022-22965CVE reference · x_refsource_MISC
- 20220401 Vulnerability in Spring Framework Affecting Cisco Products: March 2022CVE reference · vendor-advisory, x_refsource_CISCO
- https://www.oracle.com/security-alerts/cpuapr2022.htmlCVE reference · x_refsource_MISC
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0005CVE reference · x_refsource_CONFIRM
- https://cert-portal.siemens.com/productcert/pdf/ssa-254054.pdfCVE reference · x_refsource_CONFIRM
- https://www.oracle.com/security-alerts/cpujul2022.htmlCVE reference · x_refsource_MISC
- https://www.kb.cert.org/vuls/id/970766CVE reference
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-22965CVE 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.