CVE-2025-3845
Published: 21 April 2025
Summary
CVE-2025-3845 is a medium-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Markparticle Webserver. Its CVSS base score is 6.9 (Medium).
Operationally, ranked in the top 19.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
A buffer overflow vulnerability has been identified in markparticle WebServer up to version 1.0, specifically within the Buffer::HasWritten function in code/buffer/buffer.cpp. Manipulation of the writePos_ argument triggers the flaw, which is tracked under CWE-119 and CWE-120 and carries a CVSS 4.0 score of 6.9 reflecting network attackability without authentication or user interaction.
Remote unauthenticated attackers can exploit the issue to induce buffer overflow conditions, resulting in limited effects on confidentiality, integrity, and availability. Publicly available exploit details indicate the attack can be launched directly over the network.
The associated EPSS score remains flat at 0.0134 with no material increase observed after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12342
Vulnerability details
A vulnerability was found in markparticle WebServer up to 1.0. It has been declared as critical. Affected by this vulnerability is the function Buffer::HasWritten of the file code/buffer/buffer.cpp. The manipulation of the argument writePos_ leads to buffer overflow. The attack…
more
can be launched remotely. The exploit has been disclosed to the public and may be used.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.