Skip to content

Below has Incorrect Permission Assignment for Critical Resource

High severity GitHub Reviewed Published Mar 11, 2025 in facebookincubator/below • Updated Mar 12, 2025

Package

cargo below (Rust)

Affected versions

< 0.9.0

Patched versions

0.9.0

Description

Impact

A privilege escalation vulnerability existed in the Below service prior to v0.9.0 due to the creation of a world-writable directory at /var/log/below. This could have allowed local unprivileged users to escalate to root privileges through symlink attacks that manipulate files such as /etc/shadow.

Patches

facebookincubator/below@10e73a2

This is included in version 0.9.0

Workarounds

Change the permission on /var/log/below manually

References

https://www.facebook.com/security/advisories/cve-2025-27591
https://www.cve.org/CVERecord?id=CVE-2025-27591

References

@michel-slm michel-slm published to facebookincubator/below Mar 11, 2025
Published to the GitHub Advisory Database Mar 11, 2025
Reviewed Mar 11, 2025
Last updated Mar 12, 2025

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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Weaknesses

CVE ID

CVE-2025-27591

GHSA ID

GHSA-9mc5-7qhg-fp3w

Source code

Credits

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