Remote code execution via bit-byte bounds confusion
Published Nov 29, 2025 · Updated Dec 1, 2025
Heap buffer overflow in AIS::Message in jvde-github AIS-catcher before 0.64 allows remote attackers to execute arbitrary code via oversized packets. The setUint and setText methods compare byte counts against a bit-based maximum, permitting writes of up to 1,024 bytes into the 128-byte data array. Unauthenticated network access is sufficient; corrupting an adjacent NMEA vector yields arbitrary read/write and control-flow hijacking, while simpler input crashes the service.
Summary
What happened
Heap buffer overflow in AIS::Message in jvde-github AIS-catcher before 0.64 allows remote attackers to execute arbitrary code via oversized packets. The setUint and setText methods compare byte counts against a bit-based maximum, permitting writes of up to 1,024 bytes into the 128-byte data array. Unauthenticated network access is sufficient; corrupting an adjacent NMEA vector yields arbitrary read/write and control-flow hijacking, while simpler input crashes the service.
The record
- CVE
- CVE-2025-66216
- Published
- Nov 29, 2025
- Updated
- Dec 1, 2025
- Vendor
- jvde-github
- Product
- AIS-catcher
- Classifications
- CWE-131, CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2025CVE publishedPublication date reported by the CVE source.
- Dec 1, 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=< 0.64
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
- GHSA crash 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