# CVE-2009-5112: Information disclosure in n/a

> Remote attackers can obtain the installation path of WebGlimpse via a crafted request, exposing sensitive system information.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v64f-mchw-j235

## What is CVE-2009-5112?

CVE-2009-5112 is a medium-severity vulnerability in n/a, published on 19 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wgarcmin.cgi in WebGlimpse 2.18.7 and earlier allows remote attackers to obtain the installation path via a crafted request.

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

## Which versions are affected by CVE-2009-5112?

It affects 1 product.


Products: Iwork Webglimpse.

## How do I fix CVE-2009-5112?

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

## Is CVE-2009-5112 being exploited?

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

Public exploit code:

- WebGlimpse 2.x - 'wgarcmin.cgi' Full Path Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-5114](https://insights.sbomify.com/CVE-2009-5114/): Path traversal in n/a (medium 5.0)
- [CVE-2009-5113](https://insights.sbomify.com/CVE-2009-5113/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5112 and fix it if it is affected.

What it is: CVE-2009-5112 is a medium-severity vulnerability in n/a, published on 19 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-5112 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-2009-5112/ (Markdown: https://insights.sbomify.com/CVE-2009-5112/index.md)
```

## Sources

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

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