# CVE-2005-3344: Hardcoded credentials in n/a

> Remote attackers can gain administrative access to Horde due to a default account with a blank password.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-884-1, GHSA-cr9c-2963-c5q4

## What is CVE-2005-3344?

CVE-2005-3344 is a critical vulnerability in n/a, published on 16 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default installation of Horde 3.0.4 contains an administrative account with a blank password, which allows remote attackers to gain access.

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

It affects 1 product.


Products: Horde Horde.

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

Apply the vendor's patch.

## Is CVE-2005-3344 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3344 exists.

Public exploit code:

- Horde Groupware Unauthenticated Admin Access (nuclei): http/cves/2005/CVE-2005-3344.yaml

## Other vulnerabilities in n/a

- [CVE-2002-0181](https://insights.sbomify.com/CVE-2002-0181/): Cross-site scripting in n/a (high 7.5)
- [CVE-2006-2195](https://insights.sbomify.com/CVE-2006-2195/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2003-0728](https://insights.sbomify.com/CVE-2003-0728/): Information disclosure in n/a (medium 6.4)
- [CVE-2005-3759](https://insights.sbomify.com/CVE-2005-3759/): Cross-site scripting in n/a (medium 5.8)
- [CVE-2010-1638](https://insights.sbomify.com/CVE-2010-1638/): Server-side request forgery in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3344 is a critical vulnerability in n/a, published on 16 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-3344 exists.

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-3344/ (Markdown: https://insights.sbomify.com/CVE-2005-3344/index.md)
```

## Sources

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

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