Service crash via nomath global buffer overflow
Published Jan 24, 2024 · Updated Sep 5, 2024
Global buffer overflow in Mathtex 1.05 and earlier allows remote attackers to crash its CGI service through a crafted URL query string. The nomath() path passes caret-heavy input through strreplace() and strchange(), writing beyond the 4,096-byte global sbuff array. No authentication or user interaction is required when mathtex.cgi is web-accessible; the demonstrated consequence is process termination.
Summary
What happened
Global buffer overflow in Mathtex 1.05 and earlier allows remote attackers to crash its CGI service through a crafted URL query string. The nomath() path passes caret-heavy input through strreplace() and strchange(), writing beyond the 4,096-byte global sbuff array. No authentication or user interaction is required when mathtex.cgi is web-accessible; the demonstrated consequence is process termination.
The record
- CVE
- CVE-2023-51888
- Published
- Jan 24, 2024
- Updated
- Sep 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2024CVE publishedPublication date reported by the CVE source.
- Sep 5, 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
- Mathtex nomath() global-buffer-overflow reproducerproof 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