# CVE-2004-0351: Information disclosure in n/a

> Local users with database access can decrypt sensitive data because the private key is stored alongside the public key in the Spider Sales shopping cart.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-f6g9-34fc-hhvx

## What is CVE-2004-0351?

CVE-2004-0351 is a low-severity vulnerability in n/a, published on 18 Mar 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Spider Sales shopping cart stores the private key in the same database and table as the public key, which allows local users with access to the database to decrypt data.

## Which versions are affected by CVE-2004-0351?

It affects 1 product.


Products: Spidersales Spidersales.

## How do I fix CVE-2004-0351?

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

## Is CVE-2004-0351 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0348](https://insights.sbomify.com/CVE-2004-0348/): SQL injection in n/a (critical 10.0)
- [CVE-2004-0350](https://insights.sbomify.com/CVE-2004-0350/): Weak cryptography in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0351 and fix it if it is affected.

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

## Sources

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

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