# CVE-2011-4168: Path traversal in n/a

> Remote attackers can create arbitrary files on HP Managed Printing Administration servers via directory traversal in the job delivery interface.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cqg4-2fmx-cq7w

## What is CVE-2011-4168?

CVE-2011-4168 is a high-severity path traversal vulnerability in n/a, published on 27 Dec 2011. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in hpmpa/jobDelivery/Default.asp in HP Managed Printing Administration before 2.6.4 allows remote attackers to create arbitrary files via crafted form data.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2011-4168?

It affects 1 product.


Products: Hp Managed Printing Administration.

## How do I fix CVE-2011-4168?

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

## Is CVE-2011-4168 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4166](https://insights.sbomify.com/CVE-2011-4166/): Path traversal in n/a (high 7.5)
- [CVE-2011-4167](https://insights.sbomify.com/CVE-2011-4167/): Memory corruption in n/a (high 7.5)
- [CVE-2011-4169](https://insights.sbomify.com/CVE-2011-4169/): Other in n/a (high 7.5)
- [CVE-2012-5219](https://insights.sbomify.com/CVE-2012-5219/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4168 and fix it if it is affected.

What it is: CVE-2011-4168 is a high-severity path traversal vulnerability in n/a, published on 27 Dec 2011. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4168 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-2011-4168/ (Markdown: https://insights.sbomify.com/CVE-2011-4168/index.md)
```

## Sources

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

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