# CVE-2012-0054: GoLismero symlink attack

> Local attackers can overwrite arbitrary files via symlink attacks in GoLismero, potentially compromising system integrity.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vwxc-3cfr-37jq

## What is CVE-2012-0054?

CVE-2012-0054 is a low-severity path traversal vulnerability in n/a, published on 19 Mar 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

libs/updater.py in GoLismero 0.6.3, and other versions before Git revision 2b3bb43d6867, as used in backtrack and possibly other products, allows local users to overwrite arbitrary files via a symlink attack on GoLismero-controlled files, as demonstrated using Admin/changes.dat.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2012-0054?

2 open source packages ship an affected version, including golismero. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golismero` | PyPI | All versions to 0.6.3 | None |
| `golismero` | PyPI | All versions to 0.6.3 | None |

Products: Golismero Golismero.

## How do I fix CVE-2012-0054?

No fix has been published for CVE-2012-0054 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-0054 being exploited?

There is no known exploitation of CVE-2012-0054 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0054 and fix it if it is affected.

What it is: CVE-2012-0054 is a low-severity path traversal vulnerability in n/a, published on 19 Mar 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0054 in the wild and no public exploit code.

Affected packages and fixed versions:
- golismero (PyPI): affected all versions up to 0.6.3; no fix listed
- golismero (PyPI): affected all versions up to 0.6.3; no fix listed

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-2012-0054/ (Markdown: https://insights.sbomify.com/CVE-2012-0054/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-0054
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-0054
- OSV: https://osv.dev/vulnerability/CVE-2012-0054

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-0054/
Summaries are generated and may contain mistakes; the official description above is the record.