# CVE-2007-5028: Misconfiguration in n/a

> Local attackers can read or modify sensitive files due to weak world-writable permissions in the Dibbler DHCPv6 server directory.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Sep 2007
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2007-5028, GHSA-j6fg-jv37-v833

## What is CVE-2007-5028?

CVE-2007-5028 is a high-severity vulnerability in n/a, published on 21 Sep 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dibbler 0.6.0 on Linux uses weak world-writable permissions for unspecified files in /var/lib/dibbler, which has unknown impact and local attack vectors.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Dibbler Dibbler.

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

Apply the vendor's patch.

## Is CVE-2007-5028 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5029](https://insights.sbomify.com/CVE-2007-5029/): Denial of service in n/a (medium 5.0)
- [CVE-2007-5030](https://insights.sbomify.com/CVE-2007-5030/): Integer overflow in n/a (medium 5.0)
- [CVE-2007-5031](https://insights.sbomify.com/CVE-2007-5031/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5028 is a high-severity vulnerability in n/a, published on 21 Sep 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-5028 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-5028/ (Markdown: https://insights.sbomify.com/CVE-2007-5028/index.md)
```

## Sources

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

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