VMware Spring up to 5.2.21/5.3.19 File Upload allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in VMware Spring up to 5.2.21/5.3.19. It has been rated as critical. This affects an unknown part of the component File Upload Handler. Performing a manipulation results in allocation of resources. This vulnerability was named CVE-2022-22970. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in VMware Spring up to 5.2.21/5.3.19. This affects an unknown function of the component File Upload Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability.
The weakness was presented 05/13/2022 by Rob Ryan (Website). The advisory is shared at tanzu.vmware.com. The public release was coordinated in cooperation with VMware. This vulnerability is uniquely identified as CVE-2022-22970 since 01/10/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 5.2.22 or 5.3.20 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0559). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- IBM Rational Build Forge
Product
Vendor
Name
Version
- 5.2.0
- 5.2.1
- 5.2.2
- 5.2.3
- 5.2.4
- 5.2.5
- 5.2.6
- 5.2.7
- 5.2.8
- 5.2.9
- 5.2.10
- 5.2.11
- 5.2.12
- 5.2.13
- 5.2.14
- 5.2.15
- 5.2.16
- 5.2.17
- 5.2.18
- 5.2.19
- 5.2.20
- 5.2.21
- 5.3.0
- 5.3.1
- 5.3.2
- 5.3.3
- 5.3.4
- 5.3.5
- 5.3.6
- 5.3.7
- 5.3.8
- 5.3.9
- 5.3.10
- 5.3.11
- 5.3.12
- 5.3.13
- 5.3.14
- 5.3.15
- 5.3.16
- 5.3.17
- 5.3.18
- 5.3.19
License
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (VMware): 5.3
Vendor Vector (VMware): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Spring 5.2.22/5.3.20
Timeline
01/10/2022 🔍05/13/2022 🔍
05/13/2022 🔍
03/02/2026 🔍
Sources
Vendor: vmware.comAdvisory: tanzu.vmware.com
Researcher: Rob Ryan
Status: Confirmed
Coordinated: 🔍
CVE: CVE-2022-22970 (🔍)
GCVE (CVE): GCVE-0-2022-22970
GCVE (VulDB): GCVE-100-199773
CERT Bund: WID-SEC-2026-0559 - IBM Rational Build Forge: Mehrere Schwachstellen
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 05/13/2022 10:14Updated: 03/02/2026 14:17
Changes: 05/13/2022 10:14 (47), 05/13/2022 10:16 (4), 05/15/2022 15:47 (1), 03/02/2026 14:17 (21)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.