# CVE-2015-6019: Security feature bypass in n/a

> Attackers can bypass access restrictions on ZyXEL devices by exploiting sessions that remain active after logout on unattended workstations.

- **Severity:** High 8.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/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:** 31 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-83xw-xrpp-p33r

## What is CVE-2015-6019?

CVE-2015-6019 is a high-severity vulnerability in n/a, published on 31 Dec 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The management portal on ZyXEL PMG5318-B20A devices with firmware 1.00AANC0b5 does not terminate sessions upon a logout action, which allows remote attackers to bypass intended access restrictions by leveraging an unattended workstation.

## Which versions are affected by CVE-2015-6019?

It affects 1 product.


Products: Zyxel Pmg5318-B20a Firmware.

## How do I fix CVE-2015-6019?

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

## Is CVE-2015-6019 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-6018](https://insights.sbomify.com/CVE-2015-6018/): Command injection in n/a (critical 9.8)
- [CVE-2015-6020](https://insights.sbomify.com/CVE-2015-6020/): Privilege escalation in n/a (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6019 and fix it if it is affected.

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

## Sources

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

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