CVE-2010-0118 Bournal before 1.4.1 allows local users to overwrite arbitrary files via a symlink attack on unspecified temporary files associated with a -
Low 3.3
Published
Updated
Check this codebase for CVE-2010-0118 and fix it if it is affected.
What it is: CVE-2010-0118 is a low-severity vulnerability in n/a, published on 25 Feb 2010.
Exploitation: There is no known exploitation of CVE-2010-0118 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-2010-0118/ (Markdown: https://insights.sbomify.com/CVE-2010-0118/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2010-0118?
CVE-2010-0118 is a low-severity vulnerability in n/a, published on 25 Feb 2010.
Official description
Bournal before 1.4.1 allows local users to overwrite arbitrary files via a symlink attack on unspecified temporary files associated with a --hack_the_gibson update check.
Weakness: CWE-59
Which versions are affected by CVE-2010-0118?
It affects 1 product.
Products include Becauseinter Bournal.
How do I fix CVE-2010-0118?
No fix has been published for CVE-2010-0118 yet. Limit exposure of the affected software until one is available.
Is CVE-2010-0118 being exploited?
There is no known exploitation of CVE-2010-0118 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-m5cg-xh84-2p2r.