Cyber Resilience

CVE-2025-54767

Xorux Lpar2Rrd ≤ 8.04

Public PoC
Published
29 July 2025
Modified
17 June 2026
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.053 92th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2025-54767 is a medium-severity Incorrect Use of Privileged APIs (CWE-648) vulnerability in Xorux Lpar2Rrd. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Abuse Elevation Control Mechanism (T1548); ranked in the top 8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An authenticated, read-only user can kill any processes running on the Xormon Original virtual appliance as the lpar2rrd user.

CWE(s)
CWE-648

Related Threats

MITRE ATT&CK Enterprise Techniques

T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
T1548.001 Setuid and Setgid Privilege Escalation
An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-54768Same product: Xorux Lpar2Rrd
CVE-2025-54769Same product: Xorux Lpar2Rrd
CVE-2025-54766Same vendor: Xorux
CVE-2025-54765Same vendor: Xorux
CVE-2026-41225Shared CWE-648
CVE-2026-35663Shared CWE-648
CVE-2025-23375Shared CWE-648
CVE-2026-11877Shared CWE-648
CVE-2026-35639Shared CWE-648
CVE-2025-5997Shared CWE-648

Affected Assets

xorux
lpar2rrd
≤ 8.04

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.2
  • V6.4.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover incorrect calls to privileged APIs before deployment.

AC-3 Access Enforcement partial match

Enforces authorization checks around privileged operations so that an API requiring elevated rights cannot be reached or misused without proper rights.

AC-6 Least Privilege partial match

Least-privilege assignment directly reduces both the availability of privileged APIs and the blast radius when they are invoked incorrectly.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles include correct use of privileged interfaces and safe invocation patterns that stop the weakness from being introduced.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce correct usage of privileged APIs during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect incorrect privileged API calls but does not prevent them at design time.

A.8.18 Use of privileged utility programs partial match
degrades

Restricting privileged utility programs limits the exposure of privileged APIs to misuse.

A.8.2 Privileged access rights partial match
degrades

Privileged access rights directly govern the correct use of privileged APIs and reduce misuse.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes API usage standards that can prevent incorrect privileged calls.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify correct invocation of privileged APIs.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles guide proper privilege separation and API usage.

References