Jailed-process survival via jail_remove race
Published Mar 26, 2021 · Updated Aug 4, 2024
A race condition in FreeBSD 12.2-STABLE before r369312 and 11.4-STABLE before r369313 allows remote authenticated users to leave jailed processes running. The jail_remove(2) implementation can miss processes during concurrent jail teardown, so some processes survive removal instead of being killed. The operation requires authenticated access capable of invoking jail management and can undermine isolation or service-termination expectations without proving broader host compromise.
Summary
What happened
A race condition in FreeBSD 12.2-STABLE before r369312 and 11.4-STABLE before r369313 allows remote authenticated users to leave jailed processes running. The jail_remove(2) implementation can miss processes during concurrent jail teardown, so some processes survive removal instead of being killed. The operation requires authenticated access capable of invoking jail management and can undermine isolation or service-termination expectations without proving broader host compromise.
The record
- CVE
- CVE-2020-25581
- Published
- Mar 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-362
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=FreeBSD 12.2-RELEASE before p4, 11.4-RELEASE before p8
What conditions does exploitation require?
What is affected?
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