# CVE-2016-10314: Information disclosure in n/a

> Remote attackers can read passwords by accessing a specific page on Air:Link wireless routers, exposing sensitive credentials.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 3 Apr 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hw9r-3pch-hqvv

## What is CVE-2016-10314?

CVE-2016-10314 is a high-severity vulnerability in n/a, published on 3 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jensen of Scandinavia AS Air:Link 3G (AL3G) version 2.23m (Rev. 3), Air:Link 5000AC (AL5000AC) version 1.13, and Air:Link 59300 (AL59300) version 1.04 (Rev. 4) devices allow remote attackers to read passwords via a direct request to the x.asp page.

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

## Which versions are affected by CVE-2016-10314?

It affects 3 products.


Products: Jensenofscandinavia Al3g Firmware, Jensenofscandinavia Al5000ac Firmware, Jensenofscandinavia Al59300 Firmware.

## How do I fix CVE-2016-10314?

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

## Is CVE-2016-10314 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10312](https://insights.sbomify.com/CVE-2016-10312/): Command injection in n/a (critical 9.8)
- [CVE-2016-10313](https://insights.sbomify.com/CVE-2016-10313/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-10315](https://insights.sbomify.com/CVE-2016-10315/): Open redirect in n/a (medium 6.1)
- [CVE-2016-10316](https://insights.sbomify.com/CVE-2016-10316/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10314 and fix it if it is affected.

What it is: CVE-2016-10314 is a high-severity vulnerability in n/a, published on 3 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10314 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-2016-10314/ (Markdown: https://insights.sbomify.com/CVE-2016-10314/index.md)
```

## Sources

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

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