# CVE-2007-6315: Null dereference in n/a

> Authenticated remote attackers can crash the BarracudaDrive Web Server via a malformed HTTP request causing a null pointer dereference.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/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:** 12 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vrj4-mxp7-7hwh

## What is CVE-2007-6315?

CVE-2007-6315 is a medium-severity vulnerability in n/a, published on 12 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Group Chat in BarracudaDrive Web Server before 3.8 allows remote authenticated users to cause a denial of service (crash) via a HTTP request to /eh/chat.ehintf/C. that does not contain a Connection ID, which results in a NULL pointer dereference.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Real Time Logic Barracudadrive Web Server, Real Time Logic Barracudadrive Web Server Home Server.

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

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

## Is CVE-2007-6315 being exploited?

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

Public exploit code:

- barracudadrive 3.7.2 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-6317](https://insights.sbomify.com/CVE-2007-6317/): Path traversal in n/a (medium 5.5)
- [CVE-2007-6314](https://insights.sbomify.com/CVE-2007-6314/): Information disclosure in n/a (medium 5.0)
- [CVE-2007-6316](https://insights.sbomify.com/CVE-2007-6316/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6315 is a medium-severity vulnerability in n/a, published on 12 Dec 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6315 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-2007-6315/ (Markdown: https://insights.sbomify.com/CVE-2007-6315/index.md)
```

## Sources

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

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