# CVE-2019-18922: Path traversal in n/a

> Unauthenticated attackers can read arbitrary system files via directory traversal in the web interface of this end-of-life network switch.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 29 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-48wx-hxwr-pmwh

## What is CVE-2019-18922?

CVE-2019-18922 is a high-severity path traversal vulnerability in n/a, published on 29 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Directory Traversal in the Web interface of the Allied Telesis AT-GS950/8 until Firmware AT-S107 V.1.1.3 [1.00.047] allows unauthenticated attackers to read arbitrary system files via a GET request. NOTE: This is an End-of-Life product.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-18922?

It affects 1 product.


Products: Alliedtelesis At-Gs950\/8 Firmware.

## How do I fix CVE-2019-18922?

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

## Is CVE-2019-18922 being exploited?

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

Public exploit code:

- Allied Telesis AT-GS950/8 - Local File Inclusion (nuclei): http/cves/2019/CVE-2019-18922.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18922 and fix it if it is affected.

What it is: CVE-2019-18922 is a high-severity path traversal vulnerability in n/a, published on 29 Nov 2019. 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-2019-18922 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-2019-18922/ (Markdown: https://insights.sbomify.com/CVE-2019-18922/index.md)
```

## Sources

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

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