# CVE-2005-2958: Other in n/a

> Format string vulnerabilities in the GNOME Data Access library allow attackers to execute arbitrary code.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 25 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-871-1, GHSA-jjpf-92m2-j39j

## What is CVE-2005-2958?

CVE-2005-2958 is a high-severity vulnerability in n/a, published on 25 Oct 2005. 

### Official description

Multiple format string vulnerabilities in the GNOME Data Access library for GNOME2 (libgda2) 1.2.1 and earlier allow attackers to execute arbitrary code.

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

It affects 1 product.


Products: Gnome Libgda2.

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

Apply the vendor's patch.

## Is CVE-2005-2958 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2958 is a high-severity vulnerability in n/a, published on 25 Oct 2005. 
Exploitation: There is no known exploitation of CVE-2005-2958 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-2005-2958/ (Markdown: https://insights.sbomify.com/CVE-2005-2958/index.md)
```

## Sources

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

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