# CVE-2005-0424: Missing authorization in n/a

> Remote attackers can delete guestbook messages due to insufficient authorization checks in the delete.asp script.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4qgq-3ppm-rwc7

## What is CVE-2005-0424?

CVE-2005-0424 is a medium-severity missing authorization vulnerability in n/a, published on 15 Feb 2005. It can be exploited over the network, with no action from the victim.

### Official description

Unknown vulnerability in the delete.asp program in certain versions of ASPjar Guestbook allows remote attackers to delete messages.  NOTE: there is insufficient information to know if this is the same issue as CVE-2002-1730.

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

It affects 1 product.


Products: Aspjar Aspjar Guestbook.

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

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

## Is CVE-2005-0424 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1729](https://insights.sbomify.com/CVE-2002-1729/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2002-1730](https://insights.sbomify.com/CVE-2002-1730/): Missing authorization in n/a (medium 5.0)
- [CVE-2005-0423](https://insights.sbomify.com/CVE-2005-0423/): SQL injection in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0424 is a medium-severity missing authorization vulnerability in n/a, published on 15 Feb 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0424 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-0424/ (Markdown: https://insights.sbomify.com/CVE-2005-0424/index.md)
```

## Sources

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

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