# CVE-2021-28485: Path traversal in n/a

> An authenticated attacker can exploit a path traversal vulnerability in the SIS web application to access unauthorized system files.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 14 Sep 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-r68w-x838-c65m

## What is CVE-2021-28485?

CVE-2021-28485 is a medium-severity path traversal vulnerability in n/a, published on 14 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Ericsson Mobile Switching Center Server (MSC-S) before IS 3.1 CP22, the SIS web application allows relative path traversal via a specific parameter in the https request after authentication, which allows access to files on the system that are not intended to be accessible via the web application.

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

## Which versions are affected by CVE-2021-28485?

It affects 1 product.


Products: Ericsson Mobile Switching Center Server Bc 18a Firmware.

## How do I fix CVE-2021-28485?

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

## Is CVE-2021-28485 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28485 and fix it if it is affected.

What it is: CVE-2021-28485 is a medium-severity path traversal vulnerability in n/a, published on 14 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-28485 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-2021-28485/ (Markdown: https://insights.sbomify.com/CVE-2021-28485/index.md)
```

## Sources

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

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