Code execution via unchecked fixed-buffer string operations
Published Jan 31, 2025 · Updated Feb 3, 2025
Stack buffer overflows in Qualisys C++ SDK commit a32a21a allow attackers to execute code via crafted function arguments. GetComponentString appends attacker-controlled channel text with strcat into GetCurrentFrame's 256-byte stack buffer, while SaveCapture and LoadProject use sprintf with 100-byte stack buffers. Triggering the flaw requires a caller able to supply oversized component options or file-name arguments; successful corruption can execute code, disclose data, or crash the SDK host.
Summary
What happened
Stack buffer overflows in Qualisys C++ SDK commit a32a21a allow attackers to execute code via crafted function arguments. GetComponentString appends attacker-controlled channel text with strcat into GetCurrentFrame's 256-byte stack buffer, while SaveCapture and LoadProject use sprintf with 100-byte stack buffers. Triggering the flaw requires a caller able to supply oversized component options or file-name arguments; successful corruption can execute code, disclose data, or crash the SDK host.
The record
- CVE
- CVE-2024-53320
- Published
- Jan 31, 2025
- Updated
- Feb 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 31, 2025CVE publishedPublication date reported by the CVE source.
- Feb 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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