# CVE-2005-0157: Business logic in n/a

> Attackers can subscribe arbitrary email addresses to SmartList by manipulating valid cookies, allowing unauthorized subscription management.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 May 2005
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2005-0157, DSA-720-1, GHSA-9c23-7q2q-7jv8

## What is CVE-2005-0157?

CVE-2005-0157 is a high-severity vulnerability in n/a, published on 3 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The confirm add-on in SmartList 3.15 and earlier allows attackers to subscribe arbitrary e-mail addresses by using a valid cookie that specifies an address other than the address for which the cookie was assigned.

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

It affects 1 product.


Products: Smartlist Smartlist.

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

Apply the vendor's patch.

## Is CVE-2005-0157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0157 is a high-severity vulnerability in n/a, published on 3 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0157 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-0157/ (Markdown: https://insights.sbomify.com/CVE-2005-0157/index.md)
```

## Sources

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

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