Triplecross Project maintains a focused security testing and analysis toolset, with its vulnerability footprint concentrating around the triplecross product and recurring through resource-exhaustion and memory-safety weakness classes such as unthrottled resource allocation and out-of-bounds writes. Live severity, exploitation status, and exposure metrics are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Triplecross Project over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-35505HIGH A segmentation fault in TripleCross v0.1.0 occurs when sending a control command from the client to the server. This occurs because there is no limit to the length of the output of | Aug 3, 2022 | 7.5 | 24 | NO | NO |
CVE-2022-35506HIGH TripleCross v0.1.0 was discovered to contain a stack overflow which occurs because there is no limit to the length of program parameters. | Aug 3, 2022 | 7.5 | 23 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Triplecross Project.
Media articles that mention a CVE ID that affects a product developed by Triplecross Project — matched by CVE ID, not by vendor name.