Privilege escalation via omitted Docker USER directive
Published Jun 17, 2025 · Updated Jun 17, 2025
Incorrect default permissions in conda-forge-webservices before 2025.3.24 allow attackers with command execution to run container commands as root. The Dockerfile defines no dedicated account or USER directive, so Docker selects root for the image runtime. Reachability requires a separate command-execution flaw or equivalent access; the project states that its Heroku deployment never runs containers as root.
Summary
What happened
Incorrect default permissions in conda-forge-webservices before 2025.3.24 allow attackers with command execution to run container commands as root. The Dockerfile defines no dedicated account or USER directive, so Docker selects root for the image runtime. Reachability requires a separate command-execution flaw or equivalent access; the project states that its Heroku deployment never runs containers as root.
The record
- CVE
- CVE-2025-49842
- Published
- Jun 17, 2025
- Updated
- Jun 17, 2025
- Vendor
- conda-forge
- Product
- conda-forge-webservices
- Classifications
- CWE-276
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 2025CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2025.3.24
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo