CVE-2000-0449 Weak cryptography in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2000-0449 and fix it if it is affected.
What it is: CVE-2000-0449 is a critical vulnerability in n/a, published on 15 Jun 2000.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0449 exists.
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-2000-0449/ (Markdown: https://insights.sbomify.com/CVE-2000-0449/index.md)
Omnis Studio uses trivial encoding for database fields, allowing attackers to easily decrypt and read sensitive 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-2000-0449?
CVE-2000-0449 is a critical vulnerability in n/a, published on 15 Jun 2000.
Official description
Omnis Studio 2.4 uses weak encryption (trivial encoding) for encrypting database fields.
Which versions are affected by CVE-2000-0449?
It affects 1 product.
Products include Omnis Studio.
How do I fix CVE-2000-0449?
No fix has been published for CVE-2000-0449 yet. Limit exposure of the affected software until one is available.
Is CVE-2000-0449 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0449 exists.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in n/a
Sources
Also known as GHSA-jr8c-jq2f-gfh3.