Skip to content

Improper logic change done in a refactor results in attackers being able to mint access tokens at will

Moderate
Xe published GHSA-428r-47m3-x9hx Mar 31, 2025

Package

docker Anubis (Docker)

Affected versions

< 1.15.1

Patched versions

1.15.1

Description

Impact

This affects Anubis in its default configuration. This enables attackers that know about this vulnerability to bypass Anubis at will.

Patches

Administrators should upgrade to version v1.15.1 as soon as possible.

Workarounds

Administrators cannot work around this issue.

Additional processes around handling regression tests are being added to the Anubis project.

Timeline

  • March 31, 2025 @ 19:23 UTC: PR #180 is filed. It is instantly recognized as a recurrence of CVE-2025-24369. Coordination is made downstream distributors.
  • March 31, 2024 @ 21:45 UTC: Version v1.15.1 is staged for release.
  • March 31, 2024 @ 22:30 UTC: Version v1.15.1 is released, fixing the issue. Downstream distributors are advised to patch. This advisory is released.

Severity

Moderate

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
Changed
Confidentiality
None
Integrity
None
Availability
Low

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:C/C:N/I:N/A:L

CVE ID

CVE-2025-24369

Weaknesses

Use of Uninitialized Variable

The code uses a variable that has not been initialized, leading to unpredictable or unintended results. Learn more on MITRE.

Credits