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

> Local attackers can bypass authentication in avast! Server Edition by exploiting a missing password check, gaining unauthorized access.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-769j-g48q-6jw7

## What is CVE-2007-0829?

CVE-2007-0829 is a medium-severity authentication bypass vulnerability in n/a, published on 7 Feb 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

avast! Server Edition before 4.7.726 does not demand a password in a certain intended context, even when a password has been set, which allows local users to bypass authentication requirements.

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

It affects 1 product.


Products: Alwil Avast Antivirus.

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

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

## Is CVE-2007-0829 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2869](https://insights.sbomify.com/CVE-2006-2869/): Other in n/a (critical 10.0)
- [CVE-2006-4626](https://insights.sbomify.com/CVE-2006-4626/): Memory corruption in n/a (high 7.5)
- [CVE-2005-2385](https://insights.sbomify.com/CVE-2005-2385/): Memory corruption in n/a (high 7.5)
- [CVE-2005-1719](https://insights.sbomify.com/CVE-2005-1719/): Unknown vulnerability in ALWIL avast! (high 7.5)
- [CVE-2006-1355](https://insights.sbomify.com/CVE-2006-1355/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0829 is a medium-severity authentication bypass vulnerability in n/a, published on 7 Feb 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-0829 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-0829/ (Markdown: https://insights.sbomify.com/CVE-2007-0829/index.md)
```

## Sources

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

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