# CVE-2014-10079: Information disclosure in n/a

> Vembu StoreGrid leaks private IP addresses in HTML source due to incorrect path processing, exposing internal network details to attackers.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 23 Feb 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3vx9-wcw7-gppj

## What is CVE-2014-10079?

CVE-2014-10079 is a medium-severity vulnerability in n/a, published on 23 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Vembu StoreGrid 4.4.x, the front page of the server web interface leaks the private IP address in the "ipaddress" hidden form value of the HTML source code, which is disclosed because of incorrect processing of an index.php/ trailing slash.

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

## Which versions are affected by CVE-2014-10079?

It affects 1 product.


Products: Vembu Storegrid.

## How do I fix CVE-2014-10079?

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

## Is CVE-2014-10079 being exploited?

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

Public exploit code:

- Vembu Storegrid Web Interface 4.4.0 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-10078](https://insights.sbomify.com/CVE-2014-10078/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-10079 and fix it if it is affected.

What it is: CVE-2014-10079 is a medium-severity vulnerability in n/a, published on 23 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-10079 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-2014-10079/ (Markdown: https://insights.sbomify.com/CVE-2014-10079/index.md)
```

## Sources

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

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