Security readout for executives and security teams
Plain-English summary
Some Quarkus-based REST services may process a JSON request body before checking annotation-based access rules. That means unauthenticated traffic can trigger body handling that should have happened only after authorization. The strongest stated impact is availability disruption, with lower confidentiality and integrity impact.
Executive priority
Treat as a high-priority server-side API issue for affected Quarkus deployments, especially internet-facing services. Prioritize patching and exposure review because the flaw can be reached remotely without authentication.
Technical view
CVE-2023-6267 affects REST resources secured with annotation-based security where JSON deserialization occurs before security constraints are evaluated. Configuration-based security is stated as not affected. Red Hat rates it high with CVSS 8.6, network-accessible, no privileges or user interaction required.
Likely exposure
Exposure is most likely in Red Hat build of Quarkus 2.13.9 and 3.2.9 affected builds, plus listed Red Hat products using affected RESTEasy packages. Services without JSON-consuming REST endpoints or without annotation-based security are less likely exposed.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is pre-authentication processing of attacker-supplied JSON, especially where internet-facing APIs use affected Quarkus REST resources.
Researcher notes
The key distinction is annotation-based versus configuration-based security. Evidence in the bundle does not provide exploit details, fixed version ranges, or proof of exploitation, so validation should focus on product/version mapping and endpoint security model.
Mitigation direction
- Apply applicable Red Hat errata RHSA-2024:0494 or RHSA-2024:0495 where relevant.
- Check Red Hat CVE guidance for corrected builds and product-specific status.
- Inventory affected Quarkus, RESTEasy, and RESTEasy Reactive packages.
- Consider configuration-based security as a compensating control after testing.
- Restrict unauthenticated access to affected REST endpoints where possible.
Validation and detection
- Identify services using affected Red Hat Quarkus or listed Red Hat products.
- Map REST resources that consume JSON and use annotation-based security.
- Confirm dependency versions against Red Hat CVE and errata records.
- Verify remediation through SBOM, build manifests, or runtime package inspection.
- Regression-test authorization behavior for protected JSON endpoints.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-755: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-6267 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H3.94.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2024:0494CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2024:0495CVE reference · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2023-6267CVE reference · vdb-entry, x_refsource_REDHAT
- RHBZ#2251155CVE reference · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Handling of Exceptional Conditions
Improper Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.