Process crash via invalid condition-variable destruction
Published Jul 14, 2025 · Updated Jul 15, 2025
Memory corruption in snap7-rs 1.142.0 and 1.142.1 allows local users to crash a consuming process through S7Partner API calls. The S7Partner destructor reaches pthread_cond_destroy with invalid native state after a fuzzed create, start_to, and stop call sequence. Reproduction requires a local harness that invokes unsafe Rust bindings with crafted addresses and ports; the demonstrated consequence is a segmentation fault.
Summary
What happened
Memory corruption in snap7-rs 1.142.0 and 1.142.1 allows local users to crash a consuming process through S7Partner API calls. The S7Partner destructor reaches pthread_cond_destroy with invalid native state after a fuzzed create, start_to, and stop call sequence. Reproduction requires a local harness that invokes unsafe Rust bindings with crafted addresses and ports; the demonstrated consequence is a segmentation fault.
The record
- CVE
- CVE-2025-7616
- Published
- Jul 14, 2025
- Updated
- Jul 15, 2025
- Vendor
- gmg137
- Product
- snap7-rs
- Classifications
- CWE-119, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 14, 2025CVE publishedPublication date reported by the CVE source.
- Jul 15, 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=1.142.0
- Affected versionversion=1.142.1
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
- replay_snap1 proof of conceptproof of concept · demonstrated
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