CVE-2003-1391 Weak cryptography in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2003-1391 and fix it if it is affected.
What it is: CVE-2003-1391 is a high-severity vulnerability in n/a, published on 19 Oct 2007.
Exploitation: There is no known exploitation of CVE-2003-1391 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2003-1391/ (Markdown: https://insights.sbomify.com/CVE-2003-1391/index.md)
Weak encryption and predictable keys in RTS CryptoBuddy allow attackers to guess passphrases and access protected data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2003-1391?
CVE-2003-1391 is a high-severity vulnerability in n/a, published on 19 Oct 2007.
Official description
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.
Weakness: CWE-310
Which versions are affected by CVE-2003-1391?
It affects 1 product.
Products include Research Triangle Software Cryptobuddy.
How do I fix CVE-2003-1391?
No fix has been published for CVE-2003-1391 yet. Limit exposure of the affected software until one is available.
Is CVE-2003-1391 being exploited?
There is no known exploitation of CVE-2003-1391 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-54v2-68v5-6xj9.