CVE-2022-35505: A segmentation fault in TripleCross v0.1.0 occurs when sending a control command from the client to the server

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2022-35505 is a high-severity flaw (CVSS 7.5) affecting triplecross. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 the executed command.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-770
Published	2022-08-03
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: triplecross project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-08-03 21:15 UTCPublished CVE record published
2026-06-17 04:51 UTCUpdated Record last modified

triplecross project triplecross DOWNGRADE

Affected: 0.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.1.0

1. Check installed version

apt-cache policy triplecross || rpm -q triplecross || triplecross --version

2. No fixed release: DOWNGRADE to a release before 0.1.0 (Debian / Ubuntu)

apt-cache madison triplecross sudo apt install triplecross=<VERSION_BEFORE_0.1.0> sudo apt-mark hold triplecross

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list triplecross sudo dnf downgrade triplecross-<VERSION_BEFORE_0.1.0> sudo dnf versionlock add triplecross

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-35505?

triplecross: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-35505 being exploited?

CVE-2022-35505 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-35505 affect?

CVE-2022-35505 affects triplecross. Severity is high (CVSS 7.5). 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 the executed command.

How urgent is CVE-2022-35505?

Priority 51/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-35506 HIGH 7.5 DOWNGRADE TripleCross v0.1.0 was discovered to contain a stack overflow which occurs because there is no limit to the le

References

← Back to latest CVEs