# CVE-2005-0311: Auth bypass in n/a

> Remote authenticated users retain unauthorized access to resources after administrator disables them due to failure to terminate PPTP sessions.

- **Severity:** Medium 4.6 (`AV:L/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:** No
- **Published:** 10 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8cc7-wj33-wwmw

## What is CVE-2005-0311?

CVE-2005-0311 is a medium-severity authentication bypass vulnerability in n/a, published on 10 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ingate Firewall 4.1.3 and earlier does not terminate the PPTP session for an active user when the administrator disables that user from a resource, which could allow remote authenticated users to retain unauthorized access to resources.

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

It affects 1 product.


Products: Ingate Ingate Firewall.

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

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

## Is CVE-2005-0311 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6092](https://insights.sbomify.com/CVE-2007-6092/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-6097](https://insights.sbomify.com/CVE-2007-6097/): Other in n/a (critical 10.0)
- [CVE-2007-6099](https://insights.sbomify.com/CVE-2007-6099/): Security feature bypass in n/a (critical 10.0)
- [CVE-2007-6098](https://insights.sbomify.com/CVE-2007-6098/): Information disclosure in n/a (high 7.5)
- [CVE-2003-1112](https://insights.sbomify.com/CVE-2003-1112/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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