# CVE-2008-7019: Auth bypass in n/a

> Remote attackers can bypass authentication and gain privileges by modifying specific cookies in Esqlanelapse.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gqv5-g48q-28xv

## What is CVE-2008-7019?

CVE-2008-7019 is a high-severity authentication bypass vulnerability in n/a, published on 21 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Esqlanelapse 2.6.1 and 2.6.2 allows remote attackers to bypass authentication and gain privileges via modified (1) enombre and (2) euri cookies.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2008-7019?

It affects 1 product.


Products: Esqlanelapse Esqlanelapse.

## How do I fix CVE-2008-7019?

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

## Is CVE-2008-7019 being exploited?

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

Public exploit code:

- Esqlanelapse Software Project 2.6.2 - Insecure Cookie Handling (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3560](https://insights.sbomify.com/CVE-2007-3560/): Multiple unspecified vulnerabilities in Esqlanelapse before 2.6 have unknown impact and attack vectors. (high 7.5)
- [CVE-2006-1570](https://insights.sbomify.com/CVE-2006-1570/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7019 and fix it if it is affected.

What it is: CVE-2008-7019 is a high-severity authentication bypass vulnerability in n/a, published on 21 Aug 2009. 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-2008-7019 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-2008-7019/ (Markdown: https://insights.sbomify.com/CVE-2008-7019/index.md)
```

## Sources

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

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