Skip to content
Noroxi
NVD / CVE Program· CNA vmware

CVE-2022-31690: 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…

Noroxi assessment

Priority: Monitor (action score 32/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.6% 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. Special conditions such as timing or configuration are required.
  • Fixed version: org.springframework.security:spring-security-oauth2-client (Maven) 5.7.5, 5.6.9; 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.

Low priority for now. Upgrade to org.springframework.security:spring-security-oauth2-client (Maven) 5.7.5, 5.6.9; 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, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can modify a request initiated by the Client (via the browser) to the Authorization Server which can lead to a privilege escalation on the subsequent approval. This scenario can happen if the Authorization Server responds with an OAuth2 Access Token Response containing an empty scope list (per RFC 6749, Section 5.1) on the subsequent request to the token endpoint to obtain the access token.

HighCVSS 8.1 · v3.1—No exploit Fix available
Published
Oct 31, 2022
Updated
Jun 17, 2026
EPSS
1.2% · 69th percentile
CWE
—

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CISA SSVC decision

Exploitation
none
Automatable
no
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
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-31690

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for vmware records
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
vmwarespring security
netappactive iq unified manager

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

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 Security

    • Spring Security (5.7 to 5.7.4 and 5.6 to 5.6.8 as well as older, unsupported versions)affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.springframework.security:spring-security-oauth2-clientfrom 5.7.0 · before 5.7.55.7.5
Mavenorg.springframework.security:spring-security-oauth2-clientbefore 5.6.95.6.9
Red Hat:openshift:4.10::el7openshiftbefore 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el70:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7
Red Hat:openshift:4.10::el7openshift-hyperkubebefore 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el70:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7
Red Hat:openshift:4.10::el8haproxybefore 0:2.2.19-4.el80:2.2.19-4.el8
Red Hat:openshift:4.10::el8haproxy-debugsourcebefore 0:2.2.19-4.el80:2.2.19-4.el8
Red Hat:openshift:4.10::el8haproxy22before 0:2.2.19-4.el80:2.2.19-4.el8
Red Hat:openshift:4.10::el8haproxy22-debuginfobefore 0:2.2.19-4.el80:2.2.19-4.el8
Red Hat:openshift:4.10::el8jenkinsbefore 0:2.387.1.1680701869-1.el80:2.387.1.1680701869-1.el8
Red Hat:openshift:4.10::el8jenkins-2-pluginsbefore 0:4.10.1680703106-1.el80:4.10.1680703106-1.el8
Red Hat:openshift:4.10::el8openshiftbefore 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el80:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el8
Red Hat:openshift:4.10::el8openshift-hyperkubebefore 0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el80:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el8

Same product

vmware: all records

Other 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-2022-31692Spring 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…
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2021-22119Jun 29, 2021 · Spring Security versions 5.5.x prior to 5.5.1, 5.4.x prior to 5.4.7, 5.3.x prior to 5.3.10 and 5.2.x prior to 5.2.11 are susceptible to a…
    32Monitor
  • ← 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
  • 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 / packageFixed versionSource
Maven:org.springframework.security:spring-security-oauth2-client5.6.9Package registry (OSV)
Maven:org.springframework.security:spring-security-oauth2-client5.7.5Package registry (OSV)
red hat:haproxy0:2.2.19-4.el8 · Red Hat:openshift:4.10::el8Package registry (OSV)
red hat:haproxy-debugsource0:2.2.19-4.el8 · Red Hat:openshift:4.10::el8Package registry (OSV)
red hat:haproxy220:2.2.19-4.el8 · Red Hat:openshift:4.10::el8Package registry (OSV)
red hat:haproxy22-debuginfo0:2.2.19-4.el8 · Red Hat:openshift:4.10::el8Package registry (OSV)
red hat:jenkins0:2.387.1.1680701869-1.el8 · Red Hat:openshift:4.10::el8Package registry (OSV)
red hat:jenkins-2-plugins0:4.10.1680703106-1.el8 · Red Hat:openshift:4.10::el8Package registry (OSV)
red hat:openshift0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 · Red Hat:openshift:4.10::el7Package registry (OSV)
red hat:openshift-hyperkube0:4.10.0-202303221742.p0.g16bcd69.assembly.stream.el7 · Red Hat:openshift:4.10::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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.
  • Special conditions such as timing or configuration are required.

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
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

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)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records