CVE-2005-4847 Unspecified vulnerability in Spey 0.3.3 has unknown impact and attack vectors related to "A number of security holes which could lead to com
Critical 10.0
Published
Updated
Check this codebase for CVE-2005-4847 and fix it if it is affected.
What it is: CVE-2005-4847 is a critical vulnerability in n/a, published on 20 Jun 2007.
Exploitation: There is no known exploitation of CVE-2005-4847 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-2005-4847/ (Markdown: https://insights.sbomify.com/CVE-2005-4847/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2005-4847?
CVE-2005-4847 is a critical vulnerability in n/a, published on 20 Jun 2007.
Official description
Unspecified vulnerability in Spey 0.3.3 has unknown impact and attack vectors related to "A number of security holes which could lead to compromise," a different issue than CVE-2005-4846.
Which versions are affected by CVE-2005-4847?
It affects 1 product.
Products include Spey Spey.
How do I fix CVE-2005-4847?
No fix has been published for CVE-2005-4847 yet. Limit exposure of the affected software until one is available.
Is CVE-2005-4847 being exploited?
There is no known exploitation of CVE-2005-4847 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-rgjj-vq6w-2826.