# CVE-2004-0274: Privilege escalation in n/a

> Remote attackers can exploit a status assignment flaw in Eggdrop to promote unauthorized bots to sharebot status, enabling privilege escalation and unauthorized activities.

- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0274, GHSA-j5mw-wq25-jc27

## What is CVE-2004-0274?

CVE-2004-0274 is a high-severity vulnerability in n/a, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Share.mod in Eggheads Eggdrop IRC bot 1.6.10 through 1.6.15 can mistakenly assign STAT_OFFERED status to a bot that is not a sharebot, which allows remote attackers to use STAT_OFFERED to promote a bot to a sharebot and conduct unauthorized activities.

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

It affects 1 product.


Products: Eggheads Eggdrop Irc Bot.

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

Upgrade to a fixed version.

## Is CVE-2004-0274 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2807](https://insights.sbomify.com/CVE-2007-2807/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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