Local process termination via writable PID file
Published Jun 2, 2021 · Updated Aug 4, 2024
A signal-handler race in WildFly allows local users to make a root-run JBoss EAP init script terminate arbitrary processes. The init.d script trusts a writable /var/run/jboss-eap/ PID file and passes its process identifier to a root kill operation without protecting the file against replacement. Exploitation requires local access to modify that PID file; the bounded impact is denial of service through termination of selected processes, not confidentiality or integrity compromise.
Summary
What happened
A signal-handler race in WildFly allows local users to make a root-run JBoss EAP init script terminate arbitrary processes. The init.d script trusts a writable /var/run/jboss-eap/ PID file and passes its process identifier to a root kill operation without protecting the file against replacement. Exploitation requires local access to modify that PID file; the bounded impact is denial of service through termination of selected processes, not confidentiality or integrity compromise.
The record
- CVE
- CVE-2020-14317
- Published
- Jun 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- 389 Directory Server
- Product
- WildFly
- Classifications
- CWE-364, T1489
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 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=will not be fixed
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.
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