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

> Remote attackers can read device memory to obtain administrator credentials via a specific URL pattern, leading to potential account takeover.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/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:** 7 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-54v7-6rq4-h28f

## What is CVE-2014-9303?

CVE-2014-9303 is a high-severity vulnerability in n/a, published on 7 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EntryPass N5200 Active Network Control Panel allows remote attackers to read device memory and obtain the administrator username and password via a URL starting with an ASCII character o through z or A through D, different vectors than CVE-2014-8868.

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

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

It affects 1 product.


Products: Entrypass N5200 Active Network Control Panel.

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

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

## Is CVE-2014-9303 being exploited?

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

Public exploit code:

- EntryPass N5200 - Credentials Exposure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-8868](https://insights.sbomify.com/CVE-2014-8868/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9303 is a high-severity vulnerability in n/a, published on 7 Dec 2014. 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-9303 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-9303/ (Markdown: https://insights.sbomify.com/CVE-2014-9303/index.md)
```

## Sources

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

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