# CVE-2007-5819: Missing authorization in n/a

> Local attackers can exploit weak directory permissions to inject malicious files into the update directory, potentially leading to code execution or privilege escalation.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mhrh-fcvq-wqv7

## What is CVE-2007-5819?

CVE-2007-5819 is a low-severity missing authorization vulnerability in n/a, published on 5 Nov 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Tivoli Continuous Data Protection for Files (CDP) 3.1.0 uses weak permissions (unrestricted write) for the Central Admin Global download directory, which allows local users to place arbitrary files into a location used for updating CDP clients.

Weakness: CWE-264

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

It affects 1 product.


Products: Ibm Tivoli Continuous Data Protection for Files.

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

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

## Is CVE-2007-5819 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1334](https://insights.sbomify.com/CVE-2009-1334/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5819 is a low-severity missing authorization vulnerability in n/a, published on 5 Nov 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-5819 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-5819/ (Markdown: https://insights.sbomify.com/CVE-2007-5819/index.md)
```

## Sources

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

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