Remote memory corruption via unchecked write offset
Published Apr 21, 2025 · Updated Apr 22, 2025
Buffer overflow in Markparticle WebServer 1.0 allows remote attackers to corrupt process memory through crafted HTTP traffic. Buffer::HasWritten adds a supplied length to writePos_ without checking whether the resulting offset remains inside the backing vector before later buffer operations use it. Unauthenticated network access reaches the affected HTTP server, and successful exploitation permits out-of-bounds memory writes with confidentiality, integrity, and availability effects.
Summary
What happened
Buffer overflow in Markparticle WebServer 1.0 allows remote attackers to corrupt process memory through crafted HTTP traffic. Buffer::HasWritten adds a supplied length to writePos_ without checking whether the resulting offset remains inside the backing vector before later buffer operations use it. Unauthenticated network access reaches the affected HTTP server, and successful exploitation permits out-of-bounds memory writes with confidentiality, integrity, and availability effects.
The record
- CVE
- CVE-2025-3845
- Published
- Apr 21, 2025
- Updated
- Apr 22, 2025
- Vendor
- Markparticle
- Product
- WebServer
- Classifications
- CWE-119, CWE-120, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2025CVE publishedPublication date reported by the CVE source.
- Apr 22, 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.0
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