# CVE-2005-4818: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in Copernicus Europa via multiple injection vectors, potentially compromising data integrity and confidentiality.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2006
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-3php-qpv3-6pw7

## What is CVE-2005-4818?

CVE-2005-4818 is a high-severity SQL injection vulnerability in n/a, published on 29 Dec 2006. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in Copernicus Europa allow remote attackers to execute arbitrary SQL commands via unknown vectors.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

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

It affects 1 product.


Products: Copernicus Europa.

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

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

## Is CVE-2005-4818 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4818 is a high-severity SQL injection vulnerability in n/a, published on 29 Dec 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4818 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-4818/ (Markdown: https://insights.sbomify.com/CVE-2005-4818/index.md)
```

## Sources

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

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