# CVE-2007-2849: Auth bypass in n/a

> Remote attackers can bypass authentication and log in as unregistered Active Directory users without a password, gaining unauthorized access to the document management system.

- **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:** No
- **Published:** 24 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4v5r-3fh9-hjh3

## What is CVE-2007-2849?

CVE-2007-2849 is a critical authentication bypass vulnerability in n/a, published on 24 May 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

KnowledgeTree Document Management (aka KnowledgeTree Open Source) before STABLE 3.3.7 does not require a password for an unregistered user, when the user exists in Active Directory, which allows remote attackers to log onto KTDMS without the intended authorization check.

## Which versions are affected by CVE-2007-2849?

It affects 1 product.


Products: Knowledgetree Document Management Knowledgetree Document Management.

## How do I fix CVE-2007-2849?

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

## Is CVE-2007-2849 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5857](https://insights.sbomify.com/CVE-2008-5857/): Privilege escalation in n/a (medium 6.5)
- [CVE-2008-5858](https://insights.sbomify.com/CVE-2008-5858/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2849 and fix it if it is affected.

What it is: CVE-2007-2849 is a critical authentication bypass vulnerability in n/a, published on 24 May 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-2007-2849 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-2007-2849/ (Markdown: https://insights.sbomify.com/CVE-2007-2849/index.md)
```

## Sources

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

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