Spring by VMware: Authorization Bypass Through User-Controlled Key
CVE-2022-31692 is a critical-severity authorization bypass through user-controlled key vulnerability in Spring by VMware, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Spring by VMware versions: 5.7 to 5.7.4, 5.6 to 5.6.8 and older versions. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 4.25% chance of exploitation within 30 days, which is in the top 8.8% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Spring Security to 5.6.9 or 5.7.5, whichever matches your release line, or a later version.
- Read the advisory on tanzu.vmware.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Spring by VMware | Spring by VMware | 5.7 to 5.7.4, 5.6 to 5.6.8 and older versions | Not stated |
| VMware | Spring Security | 5.6.0 up to, but not including, 5.6.9; 5.7.0 up to, but not including, 5.7.5 | 5.6.9, 5.7.5 |
| NetApp | Active Iq Unified Manager | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 3.1 | 9.8 | Critical | CISA (ADP) |
Official description
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)
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How developers prevent this class of flaw
- For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
More Authorization Bypass Through User-Controlled Key vulnerabilities (CWE-639)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- tanzu.vmware.com/security/cve-2022-31692Mitigation
Third-party and government advisories
- security.netapp.com/advisory/ntap-20221215-0010/Third Party Advisory
Other vulnerabilities in Spring by VMware
- 9.8 Critical severity
Recent Authorization Bypass Through User-Controlled Key vulnerabilities
- 7.5 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.