# CVE-2010-1457: Information disclosure in n/a

> Local attackers can read arbitrary files via error messages in gdomap, requiring an upgrade to GNUstep Base.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-1457, GHSA-fc95-fh9f-q5qq

## What is CVE-2010-1457?

CVE-2010-1457 is a medium-severity vulnerability in n/a, published on 12 May 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tools/gdomap.c in gdomap in GNUstep Base before 1.20.0 allows local users to read arbitrary files via a (1) -c or (2) -a option, which prints file contents in an error message.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2010-1457?

It affects 1 product.


Products: Gnustep Gnustep Base.

## How do I fix CVE-2010-1457?

Upgrade to a fixed version.

## Is CVE-2010-1457 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-1457 exists.

Public exploit code:

- gdomap - Multiple Local Information Disclosure Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-1620](https://insights.sbomify.com/CVE-2010-1620/): Integer overflow in the load_iface function in Tools/gdomap.c in gdomap in GNUstep Base before 1.20.0 might allow context-dependent attacker (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1457 and fix it if it is affected.

What it is: CVE-2010-1457 is a medium-severity vulnerability in n/a, published on 12 May 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-1457 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-2010-1457/ (Markdown: https://insights.sbomify.com/CVE-2010-1457/index.md)
```

## Sources

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

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