Policy bypass via SIGCONT ptrace wakeup
Published Jan 15, 2020 · Updated Aug 7, 2024
Race condition in the Linux kernel before 2.4.36-rc1 allows attackers to bypass ptrace-based syscall policies using SIGCONT signals. A SIGCONT signal wakes a TASK_STOPPED tracee, allowing its pending syscall to complete before the policy-enforcing parent can inspect or block it. A process must already be under ptrace-based policy control, and winning the narrow timing race permits one syscall to execute unchecked.
Summary
What happened
Race condition in the Linux kernel before 2.4.36-rc1 allows attackers to bypass ptrace-based syscall policies using SIGCONT signals. A SIGCONT signal wakes a TASK_STOPPED tracee, allowing its pending syscall to complete before the policy-enforcing parent can inspect or block it. A process must already be under ptrace-based policy control, and winning the narrow timing race permits one syscall to execute unchecked.
The record
- CVE
- CVE-2007-4774
- Published
- Jan 15, 2020
- Updated
- Aug 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1562.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 7, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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