Vulnerability in com.upokecenter:cbor (CVE-2024-23684)
Summary
Vulnerability in com.upokecenter:cbor (CVE-2024-23684). Risk of unauthorized operations or information disclosure. Exploitable via DecodeFromBytes. Mitigation: upgrade to 4.5.1 or later.
Original description
The description as published by the source.
Inefficient algorithmic complexity in DecodeFromBytes function in com.upokecenter.cbor Java implementation of Concise Binary Object Representation (CBOR) versions 4.0.0 to 4.5.1 allows an attacker to cause a denial of service by passing a maliciously crafted input. Depending on an application's use of this library, this may be a remote attacker.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-23684 has been found in com.upokecenter:cbor.
Attackers can target a specific entry point like DecodeFromBytes over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade com.upokecenter:cbor to 4.5.1 or later.
If unsure, ask your IT team or search "com.upokecenter:cbor CVE-2024-23684" on the vendor's site.
CVE-2024-23684 (com.upokecenter:cbor) — CWE-407 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DecodeFromBytes
Patched: 4.5.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-407) exists in com.upokecenter:cbor. Attackers reach the vulnerable code path via DecodeFromBytes without authentication.
Check the vendor advisory for the affected versions of com.upokecenter:cbor. Attack surface: DecodeFromBytes.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 4.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.upokecenter:cbor を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.upokecenter:cbor to 4.5.1ステージング環境で 4.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web repo.maven.apache.org