A flaw was found in Undertow. Servlets using a method that calls…
CVE-2024-4027 is a high-severity improper input validation vulnerability in Red Hat build of Apicurio Registry 2 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 0.4% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat build of Apicurio Registry 2 you run against the affected versions below, and install the vendor's latest release.
- 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 |
|---|---|---|---|
| Red Hat | Red Hat build of Apicurio Registry 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Quarkus | Not specified in the record | Not stated |
| Red Hat | Red Hat Data Grid 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Fuse 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Integration Camel K 1 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform Expansion Pack | Not specified in the record | Not stated |
| Red Hat | Red Hat Process Automation 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Single Sign-On 7 | 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
- 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 CNA (redhat.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (redhat.com) |
| CVSS 3.1 | 7.5 | High | CNA |
Official description
A flaw was found in Undertow. Servlets using a method that calls HttpServletRequestImpl.getParameterNames() can cause an OutOfMemoryError when the client sends a request with large parameter names. This issue can be exploited by an unauthorized user to cause a remote denial-of-service (DoS) attack.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
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
Other references
Other vulnerabilities in Red Hat build of Apicurio Registry 2
- 7.5 High severity
- 9.1 Critical severity
- 9.8 Critical severity
- 9.1 Critical severity
- 7.5 High severity
- 9.1 Critical severity
Recent Improper Input Validation vulnerabilities
- 7.5 High severity
- 7.1 High severity
- 8.3 High severity
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.