Skip to content

Duplicate Advisory: Inefficient Algorithmic Complexity in com.upokecenter:cbor

High severity GitHub Reviewed Published Jan 19, 2024 to the GitHub Advisory Database • Updated Jan 22, 2026
Withdrawn This advisory was withdrawn on Jan 22, 2026

Package

maven com.upokecenter:cbor (Maven)

Affected versions

>= 4.0.0, < 4.5.1

Patched versions

4.5.1

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-36p8-mvp6-cv38. This link is maintained to preserve external references.

Original Description

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.

References

Published by the National Vulnerability Database Jan 19, 2024
Published to the GitHub Advisory Database Jan 19, 2024
Reviewed Jan 23, 2024
Withdrawn Jan 22, 2026
Last updated Jan 22, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Weaknesses

Inefficient Algorithmic Complexity

An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-hfj8-63c8-rmfw

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.