CVE-2022-31692: Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or…
Noroxi assessment
Priority: Plan (action score 40/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.2% (FIRST EPSS); higher than 91.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: org.springframework.security:spring-security-core (Maven) 5.6.9, 5.7.5; openshift (Red Hat:openshift:4.10::el7) 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7; openshift-hyperkube (Red Hat:openshift:4.10::el7) 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7.
Add it to your regular patch cycle. Upgrade to org.springframework.security:spring-security-core (Maven) 5.6.9, 5.7.5; openshift (Red Hat:openshift:4.10::el7) 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7; openshift-hyperkube (Red Hat:openshift:4.10::el7) 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or include dispatcher types. Specifically, an application is vulnerable when all of the following are true: The application expects that Spring Security applies security to forward and include dispatcher types. The application uses the AuthorizationFilter either manually or via the authorizeHttpRequests() method. The application configures the FilterChainProxy to apply to forward and/or include requests (e.g. spring.security.filter.dispatcher-types = request, error, async, forward, include). The application may forward or include the request to a higher privilege-secured endpoint.The application configures Spring Security to apply to every dispatcher type via authorizeHttpRequests().shouldFilterAllDispatcherTypes(true)
- Published
- Oct 31, 2022
- Updated
- Jun 17, 2026
- EPSS
- 4.2% · 91th percentile
- CWE
- CWE-639
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vmware | spring security | cpe:2.3:a:vmware:spring_security |
| netapp | active iq unified manager | cpe:2.3:a:netapp:active_iq_unified_manager |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.
n/a Spring by VMware
- 5.7 to 5.7.4, 5.6 to 5.6.8 and older versionsaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netapp active iq unified managerall versions
- vmware spring security5.6.0 and later · before 5.6.9
- vmware spring security5.7.0 and later · before 5.7.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.springframework.security:spring-security-core | from 5.6.0 · before 5.6.9 | 5.6.9 |
| Maven | org.springframework.security:spring-security-core | from 5.7.0 · before 5.7.5 | 5.7.5 |
| Red Hat:openshift:4.10::el7 | openshift | before 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 | 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 |
| Red Hat:openshift:4.10::el7 | openshift-hyperkube | before 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 | 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 |
| Red Hat:openshift:4.10::el8 | haproxy | before 0:2.2.19-4.el8 | 0:2.2.19-4.el8 |
| Red Hat:openshift:4.10::el8 | haproxy-debugsource | before 0:2.2.19-4.el8 | 0:2.2.19-4.el8 |
| Red Hat:openshift:4.10::el8 | haproxy22 | before 0:2.2.19-4.el8 | 0:2.2.19-4.el8 |
| Red Hat:openshift:4.10::el8 | haproxy22-debuginfo | before 0:2.2.19-4.el8 | 0:2.2.19-4.el8 |
| Red Hat:openshift:4.10::el8 | jenkins | before 0:2.387.1.1680701869-1.el8 | 0:2.387.1.1680701869-1.el8 |
| Red Hat:openshift:4.10::el8 | jenkins-2-plugins | before 0:4.10.1680703106-1.el8 | 0:4.10.1680703106-1.el8 |
| Red Hat:openshift:4.10::el8 | openshift | before 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el8 | 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el8 |
| Red Hat:openshift:4.10::el8 | openshift-hyperkube | before 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el8 | 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el8 |
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-22978In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be…43Plan
- CVE-2023-34034Using "**" as a pattern in Spring Security configuration
for WebFlux creates a mismatch in pattern matching between Spring
Security and…40Plan
- CVE-2014-3527When using the CAS Proxy ticket authentication from Spring Security 3.1 to 3.2.4 a malicious CAS Service could trick another CAS Service…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-22976May 19, 2022 · Spring Security versions 5.5.x prior to 5.5.7, 5.6.x prior to 5.6.4, and earlier unsupported versions contain an integer overflow…22Monitor
- ← EarlierCVE-2022-31690Oct 31, 2022 · Spring Security, versions 5.7 prior to 5.7.5, and 5.6 prior to 5.6.9, and older unsupported versions could be susceptible to a privilege…32Monitor
- Later →CVE-2023-20862Apr 19, 2023 · In Spring Security, versions 5.7.x prior to 5.7.8, versions 5.8.x prior to 5.8.3, and versions 6.0.x prior to 6.0.3, the logout support…25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.springframework.security:spring-security-core | 5.6.9 | Package registry (OSV) |
| Maven:org.springframework.security:spring-security-core | 5.7.5 | Package registry (OSV) |
| red hat:haproxy | 0:2.2.19-4.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:haproxy-debugsource | 0:2.2.19-4.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:haproxy22 | 0:2.2.19-4.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:haproxy22-debuginfo | 0:2.2.19-4.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:jenkins | 0:2.387.1.1680701869-1.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:jenkins-2-plugins | 0:4.10.1680703106-1.el8 · Red Hat:openshift:4.10::el8 | Package registry (OSV) |
| red hat:openshift | 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 · Red Hat:openshift:4.10::el7 | Package registry (OSV) |
| red hat:openshift-hyperkube | 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 · Red Hat:openshift:4.10::el7 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:35 | 2022-11-03 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-10-29 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+2 d
- TodayNov 16, 2026+1477 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-639 · Authorization Bypass Through User-Controlled KeyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.
The bug in code
The whole CWE-639 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const invoice = await Invoice.findById(req.params.id);
res.json(invoice);Fixed
const invoice = await Invoice.findOne({
id: req.params.id,
ownerId: req.user.id,
});
if (!invoice) return res.sendStatus(404);
res.json(invoice);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.