CVE-2003-1391: RTS CryptoBuddy 1.0 and 1.2 uses a weak encryption algorithm for the passphrase and generates predictable keys

This month

HIGH 7.5DOWNGRADE

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

RTS CryptoBuddy 1.0 and 1.2 uses a weak encryption algorithm for the passphrase and generates predictable keys, which makes it easier for attackers to guess the passphrase.

Why this priority

High severity

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

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-310
Published	2003-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: research triangle software

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

Am I affected?

Timeline

2003-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:04 UTCUpdated Record last modified

research triangle software cryptobuddy DOWNGRADE

Affected: 1.0 · 1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

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

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

apt-cache madison cryptobuddy sudo apt install cryptobuddy=<VERSION_BEFORE_1.0> sudo apt-mark hold cryptobuddy

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

dnf --showduplicates list cryptobuddy sudo dnf downgrade cryptobuddy-<VERSION_BEFORE_1.0> sudo dnf versionlock add cryptobuddy

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-2003-1391?

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

Is CVE-2003-1391 being exploited?

CVE-2003-1391 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-2003-1391 affect?

CVE-2003-1391 affects cryptobuddy. Severity is high (CVSS 7.5). RTS CryptoBuddy 1.0 and 1.2 uses a weak encryption algorithm for the passphrase and generates predictable keys, which makes it easier for attackers to guess the passphrase.

How urgent is CVE-2003-1391?

Priority 40/100. High severity

Related CVEs

CVE-2003-1392 MEDIUM 6.6 DOWNGRADE MITIGATE CryptoBuddy 1.0 and 1.2 does not use the user-supplied passphrase to encrypt data, which could allow local use
CVE-2003-1390 HIGH 7.5 DOWNGRADE RTS CryptoBuddy 1.2 and earlier stores bytes 53 through 55 of a 55-byte passphrase in plaintext, which makes i
CVE-2003-1389 HIGH 7.5 DOWNGRADE RTS CryptoBuddy 1.2 and earlier truncates long passphrases without warning the user, which may make it easier

References

← Back to latest CVEs