Security readout for executives and security teams
Plain-English summary
CVE-2024-21909 is a high-severity denial-of-service flaw in PeterO.Cbor. Crafted CBOR data passed into DecodeFromBytes or other decoding paths can make an application unavailable. Business risk is highest where services decode untrusted CBOR from remote or unauthenticated users.
Executive priority
Treat as a high-priority availability risk if PeterO.Cbor is used on internet-facing or unauthenticated input paths. It is less urgent for internal-only uses that never decode untrusted data, but dependency owners should still remediate.
Technical view
PeterO.Cbor versions 4.0.0 through 4.5.0 are reported vulnerable. The issue is CWE-407 with CVSS 3.1 score 7.5: network reachable, low complexity, no privileges, no user interaction, and high availability impact. Sources reference a patch commit and a v4.5 to v4.5.1 comparison.
Likely exposure
Exposure is likely in .NET applications or services that include PeterO.Cbor 4.0.0 through 4.5.0 and decode attacker-controlled CBOR bytes, especially through public APIs, message ingestion, or unauthenticated request handling.
Exploitation context
The sources describe crafted input triggering denial of service through decoding mechanisms. The bundle does not show CISA KEV listing or cited evidence of active exploitation, so active exploitation should not be assumed.
Researcher notes
Evidence supports denial of service, not confidentiality or integrity impact. The affected range is stated as 4.0.0 through 4.5.0, while one affected record entry lists 4.0.0; rely on vendor advisory and package review for exact scope.
Mitigation direction
- Inventory applications using PeterO.Cbor and identify versions 4.0.0 through 4.5.0.
- Prioritize upgrading to the patched release path referenced by v4.5.1 guidance.
- Restrict unauthenticated access to endpoints that decode CBOR where practical.
- Apply request size, timeout, and resource controls around CBOR decoding paths.
- Monitor vendor advisory pages for any newer guidance or corrected affected-version details.
Validation and detection
- Check dependency manifests and lockfiles for PeterO.Cbor versions 4.0.0 through 4.5.0.
- Trace public or unauthenticated routes that call DecodeFromBytes or other CBOR decoders.
- Confirm production builds deploy the remediated dependency version.
- Review logs and telemetry for unusual decode failures or availability spikes.
- Document compensating controls for any service that cannot upgrade immediately.
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-407: 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-2024-21909 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
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
SSVC decision data
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:N/I:N/A:H3.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/peteroupc/CBOR/security/advisories/GHSA-6r92-cgxc-r5fgCVE reference, VulnCheck · vendor-advisory
- https://github.com/peteroupc/CBOR/commit/b4117dbbb4cd5a4a963f9d0c9aa132f033e15b95CVE reference, VulnCheck · patch
- https://github.com/peteroupc/CBOR/compare/v4.5...v4.5.1CVE reference, VulnCheck · related
- https://github.com/advisories/GHSA-6r92-cgxc-r5fgCVE reference, VulnCheck · vendor-advisory
- https://vulncheck.com/advisories/vc-advisory-GHSA-6r92-cgxc-r5fgCVE reference, VulnCheck · third-party-advisory
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.
Inefficient Algorithmic Complexity
Inefficient Algorithmic Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.