Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-57847 medium CVSS 6.4

Vulnerability in Ansible Automation Platform (CVE-2025-57847)

Summary

Vulnerability in Ansible Automation Platform (CVE-2025-57847). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

A container privilege escalation flaw was found in certain Ansible Automation Platform images. This issue arises from the /etc/passwd file being created with group-writable permissions during the build process. In certain conditions, an attacker who can execute commands within an affected container, even as a non-root user, can leverage their membership in the root group to modify the /etc/passwd file. This vulnerability allows an attacker to add a new user with any arbitrary UID, including UID 0, gaining full root privileges within the container.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-57847 has been found in Ansible Automation Platform.
Successful exploitation can lead to full system takeover. CVSS score: 6.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Ansible Automation Platform CVE-2025-57847" on the vendor's site.

CVE-2025-57847 (Ansible Automation Platform) — CWE-276 / CVSS v3 6.4
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-276) exists in Ansible Automation Platform.

📍 Affected scope

Check the vendor advisory for the affected versions of Ansible Automation Platform.

🔥 Severity

Severity: Medium (CVSS 6.4/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Ansible Automation Platform を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details