Red Hat build of Quarkus 2.13.9.Final: Improper Handling of Exceptional Conditions
CVE-2023-6267 is a critical-severity improper handling of exceptional conditions vulnerability in Red Hat build of Quarkus 2.13.9.Final from Red Hat, 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. There is no confirmed exploitation so far. EPSS estimates a 0.72% chance of exploitation within 30 days, higher than 54% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Quarkus to 2.13.9 or 3.2.9, whichever matches your release line, 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
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Red Hat | Red Hat build of Quarkus 2.13.9.Final | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Quarkus 3.2.9.Final | Not specified in the record | Not stated |
| Red Hat | Red Hat build of OptaPlanner 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 Integration Camel Quarkus 2 | Not specified in the record | Not stated |
| Quarkus | Quarkus | before 2.13.9; 3.0.0 up to, but not including, 3.2.9; 2.13.9; 3.2.9 | 2.13.9, 3.2.9 |
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 | 8.6 | High | CNA (redhat.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
A flaw was found in the json payload. If annotation based security is used to secure a REST resource, the JSON body that the resource may consume is being processed (deserialized) prior to the security constraints being evaluated and applied. This does not happen with configuration based security.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Handling of Exceptional Conditions
The product does not handle or incorrectly handles an exceptional condition.
More Improper Handling of Exceptional Conditions vulnerabilities (CWE-755)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Recent Improper Handling of Exceptional Conditions vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.