# CVE-2002-2303: Weak cryptography in n/a

> Remote attackers can modify shopping cart prices by decrypting client-side encrypted cookies, allowing unauthorized price manipulation in ShopFactory.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:C/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4jjv-8vv6-97v7

## What is CVE-2002-2303?

CVE-2002-2303 is a high-severity vulnerability in n/a, published on 18 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

3D3.Com ShopFactory 5.8 uses client-side encryption and decryption for sensitive price data, which allows remote attackers to modify shopping cart prices by using the Javascript to decrypt the cookie that contains the data.

Weakness: CWE-310

## Which versions are affected by CVE-2002-2303?

It affects 1 product.


Products: 3d3.com Shopfactory.

## How do I fix CVE-2002-2303?

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

## Is CVE-2002-2303 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2302](https://insights.sbomify.com/CVE-2002-2302/): Business logic in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2303 and fix it if it is affected.

What it is: CVE-2002-2303 is a high-severity vulnerability in n/a, published on 18 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-2303 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-2002-2303/ (Markdown: https://insights.sbomify.com/CVE-2002-2303/index.md)
```

## Sources

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

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