Red Hat Fuse 7.12.1: Memory Allocation with Excessive Size Value
CVE-2023-3223 is a high-severity memory allocation with excessive size value vulnerability in Red Hat Fuse 7.12.1 from Red Hat, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 2.66% chance of exploitation within 30 days, higher than 86% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Undertow to 2.2.24 or a later version.
- Read the advisory on access.redhat.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
Version data comes from the organisation that assigned the CVE; 3 further products are omitted here. 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
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (redhat.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
A flaw was found in undertow. Servlets annotated with @MultipartConfig may cause an OutOfMemoryError due to large multipart content. This may allow unauthorized users to cause remote Denial of Service (DoS) attack. If the server uses fileSizeThreshold to limit the file size, it's possible to bypass the limit by setting the file name in the request to null.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Memory Allocation with Excessive Size Value
The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.
How developers prevent this class of flaw
- Perform adequate input validation against any value that influences the amount of memory that is allocated. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to be used if necessary.
- Run your program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.
More Memory Allocation with Excessive Size Value vulnerabilities (CWE-789)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- access.redhat.com/errata/RHSA-2023:4505
- access.redhat.com/errata/RHSA-2023:4506
- access.redhat.com/errata/RHSA-2023:4507
- access.redhat.com/errata/RHSA-2023:4509
- access.redhat.com/errata/RHSA-2023:4918
- access.redhat.com/errata/RHSA-2023:4919
- access.redhat.com/errata/RHSA-2023:4920
- access.redhat.com/errata/RHSA-2023:4921
- access.redhat.com/errata/RHSA-2023:4924
- access.redhat.com/security/cve/CVE-2023-3223
- bugzilla.redhat.com/show_bug.cgi?id=2209689Issue Tracking
Other references
Recent Memory Allocation with Excessive Size Value vulnerabilities
- 7.5 High severity
Spotted an error? Tell us.