# CVE-2018-17060: Improper Access Control in Telerik Extensions

> Remote attackers can access files within the server's web directory due to lack of request whitelisting in the obsolete Telerik Extensions for ASP.NET MVC.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 8 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8h7p-qjv8-9mp4

## What is CVE-2018-17060?

CVE-2018-17060 is a medium-severity path traversal vulnerability in n/a, published on 8 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Telerik Extensions for ASP.NET MVC (all versions) does not whitelist requests, which can allow a remote attacker to access files inside the server's web directory.  NOTE: this product has been obsolete since June 2013.

## Which versions are affected by CVE-2018-17060?

2 open source packages ship an affected version, including TelerikMvcExtensions. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `TelerikMvcExtensions` | NuGet | All versions to 2013.1.219 | None |
| `TelerikMvcExtensions` | NuGet | All versions to 2013.1.219 | None |

Products: Progress Telerik Extensions for Asp.net Mvc.

## How do I fix CVE-2018-17060?

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

## Is CVE-2018-17060 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17060 and fix it if it is affected.

What it is: CVE-2018-17060 is a medium-severity path traversal vulnerability in n/a, published on 8 Oct 2018. 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-2018-17060 in the wild and no public exploit code.

Affected packages and fixed versions:
- TelerikMvcExtensions (NuGet): affected all versions up to 2013.1.219; no fix listed
- TelerikMvcExtensions (NuGet): affected all versions up to 2013.1.219; no fix listed

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-2018-17060/ (Markdown: https://insights.sbomify.com/CVE-2018-17060/index.md)
```

## Sources

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

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