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

> Remote attackers can bypass authentication via a DCRABBIT cookie to power-cycle connected devices, affecting Dataprobe iBootBar users.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2017
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-88qx-mx9f-rxcf

## What is CVE-2007-6759?

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

### Official description

Dataprobe iBootBar (with 2007-09-20 and possibly later released firmware) allows remote attackers to bypass authentication, and conduct power-cycle attacks on connected devices, via a DCRABBIT cookie.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Dataprobe Ibootbar Firmware.

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

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

## Is CVE-2007-6759 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6760](https://insights.sbomify.com/CVE-2007-6760/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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