CVE-2025-32955

Harden-Runner is a CI/CD security agent that works like an EDR for GitHub Actions runners. Versions from 0.12.0 to before 2.12.0 are vulnerable to `disable-sudo` bypass. Harden-Runner includes a policy option `disable-sudo` to prevent the GitHub Actions runner user from using sudo. This is implemented by removing the runner user from the sudoers file. However, this control can be bypassed as the runner user, being part of the docker group, can interact with the Docker daemon to launch privileged containers or access the host filesystem. This allows the attacker to regain root access or restore the sudoers file, effectively bypassing the restriction. This issue has been patched in version 2.12.0.

CVSS v3 6.0 MEDIUM

6.0^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 0.8 / Impact : 5.2

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required HIGH

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://github.com/step-security/harden-runner/commit/0634a2670c59f64b4a01f0f96f84700a4088b9f0
https://github.com/step-security/harden-runner/releases/tag/v2.12.0
https://github.com/step-security/harden-runner/security/advisories/GHSA-mxr3-8whj-j74r

Configurations

No configuration.

History

No history.

Information

Published : 2025-04-21 21:15

Updated : 2025-04-23 14:08

NVD link : CVE-2025-32955

Mitre link : CVE-2025-32955

CVE.ORG link : CVE-2025-32955

JSON object : View

Products Affected

No product.

CWE

CWE-268

Privilege Chaining

CWE-269

Improper Privilege Management

{"id": "CVE-2025-32955", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "[email protected]", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.0, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "HIGH", "confidentialityImpact": "NONE"}, "impactScore": 5.2, "exploitabilityScore": 0.8}]}, "published": "2025-04-21T21:15:20.507", "references": [{"url": "https://github.com/step-security/harden-runner/commit/0634a2670c59f64b4a01f0f96f84700a4088b9f0", "source": "[email protected]"}, {"url": "https://github.com/step-security/harden-runner/releases/tag/v2.12.0", "source": "[email protected]"}, {"url": "https://github.com/step-security/harden-runner/security/advisories/GHSA-mxr3-8whj-j74r", "source": "[email protected]"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "[email protected]", "description": [{"lang": "en", "value": "CWE-268"}, {"lang": "en", "value": "CWE-269"}]}], "descriptions": [{"lang": "en", "value": "Harden-Runner is a CI/CD security agent that works like an EDR for GitHub Actions runners. Versions from 0.12.0 to before 2.12.0 are vulnerable to `disable-sudo` bypass. Harden-Runner includes a policy option `disable-sudo` to prevent the GitHub Actions runner user from using sudo. This is implemented by removing the runner user from the sudoers file. However, this control can be bypassed as the runner user, being part of the docker group, can interact with the Docker daemon to launch privileged containers or access the host filesystem. This allows the attacker to regain root access or restore the sudoers file, effectively bypassing the restriction. This issue has been patched in version 2.12.0."}, {"lang": "es", "value": "Harden-Runner es un agente de seguridad de CI/CD que funciona como un EDR para ejecutores de GitHub Actions. Las versiones desde la 0.12.0 hasta anteriores a la 2.12.0 son vulnerables a la omisi\u00f3n de `disable-sudo`. Harden-Runner incluye la opci\u00f3n de pol\u00edtica `disable-sudo` para impedir que el usuario ejecutor de GitHub Actions use sudo. Esto se implementa eliminando al usuario ejecutor del archivo `sudoers`. Sin embargo, este control puede omitirse, ya que el usuario ejecutor, al formar parte del grupo Docker, puede interactuar con el daemon de Docker para lanzar contenedores privilegiados o acceder al sistema de archivos del host. Esto permite al atacante recuperar el acceso root o restaurar el archivo `sudoers`, evadiendo as\u00ed la restricci\u00f3n. Este problema se ha corregido en la versi\u00f3n 2.12.0."}], "lastModified": "2025-04-23T14:08:13.383", "sourceIdentifier": "[email protected]"}