CVE-2006-1865 Argument injection vulnerability in Beagle before 0.2.5 allows attackers to execute arbitrary commands via crafted filenames that inject com
High 7.5
Published
Updated
Check this codebase for CVE-2006-1865 and fix it if it is affected.
What it is: CVE-2006-1865 is a high-severity vulnerability in n/a, published on 21 Apr 2006.
Exploitation: There is no known exploitation of CVE-2006-1865 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-2006-1865/ (Markdown: https://insights.sbomify.com/CVE-2006-1865/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2006-1865?
CVE-2006-1865 is a high-severity vulnerability in n/a, published on 21 Apr 2006.
Official description
Argument injection vulnerability in Beagle before 0.2.5 allows attackers to execute arbitrary commands via crafted filenames that inject command line arguments when Beagle launches external helper applications while indexing.
Weakness: CWE-88
Which versions are affected by CVE-2006-1865?
It affects 1 product.
Products include Beagle Project Beagle.
How do I fix CVE-2006-1865?
Upgrade to a fixed version.
Is CVE-2006-1865 being exploited?
There is no known exploitation of CVE-2006-1865 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2006-1865, GHSA-9cg4-j3w9-fwph.