# CVE-2011-3829: Information disclosure in n/a

> Authenticated users can obtain sensitive installation path information via error messages in the file upload component.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **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:** 29 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7365-f7j8-fr6c

## What is CVE-2011-3829?

CVE-2011-3829 is a medium-severity vulnerability in n/a, published on 29 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ftp_upload_file.php in Support Incident Tracker (aka SiT!) 3.65 allows remote authenticated users to obtain sensitive information via the file name, which reveals the installation path in an error message.

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

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

It affects 1 product.


Products: Sitracker Support Incident Tracker.

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

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

## Is CVE-2011-3829 being exploited?

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

Public exploit code:

- Support Incident Tracker Remote Command Execution (metasploit)
- Support Incident Tracker 3.65 - Remote Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5635](https://insights.sbomify.com/CVE-2007-5635/): Multiple unspecified vulnerabilities in Salford Software Support Incident Tracker (SiT!) before 3.30 have unknown impact and attack vectors. (critical 10.0)
- [CVE-2011-3831](https://insights.sbomify.com/CVE-2011-3831/): SQL injection in n/a (high 7.5)
- [CVE-2011-4337](https://insights.sbomify.com/CVE-2011-4337/): Code injection in n/a (high 7.5)
- [CVE-2011-5071](https://insights.sbomify.com/CVE-2011-5071/): SQL injection in n/a (high 7.5)
- [CVE-2011-5072](https://insights.sbomify.com/CVE-2011-5072/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3829 is a medium-severity vulnerability in n/a, published on 29 Jan 2012. 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-2011-3829 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-2011-3829/ (Markdown: https://insights.sbomify.com/CVE-2011-3829/index.md)
```

## Sources

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

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