# CVE-2005-1424: Information disclosure in n/a

> Local attackers can read sensitive user data stored in plaintext in the GoText application's binary file.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/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:** No
- **Published:** 3 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fm6x-9f33-mpj8

## What is CVE-2005-1424?

CVE-2005-1424 is a low-severity vulnerability in n/a, published on 3 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

StumbleInside GoText 1.01 stores sensitive username, mail address,and phone number information in plaintext in the GoText.bin file, which allows local users to obtain that information.

## Which versions are affected by CVE-2005-1424?

It affects 1 product.


Products: Stumbleinside Gotext.

## How do I fix CVE-2005-1424?

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

## Is CVE-2005-1424 being exploited?

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

Public exploit code:

- GoText 1.01 - Local User Informations Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1424 and fix it if it is affected.

What it is: CVE-2005-1424 is a low-severity vulnerability in n/a, published on 3 May 2005. 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-2005-1424 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-2005-1424/ (Markdown: https://insights.sbomify.com/CVE-2005-1424/index.md)
```

## Sources

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

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