# CVE-2017-14948: Memory corruption in n/a

> Remote attackers can execute arbitrary code on D-Link routers via a buffer overflow in the fileaccess.cgi component triggered by a crafted HTTP request.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6447-8xgh-93jm

## What is CVE-2017-14948?

CVE-2017-14948 is a critical memory corruption vulnerability in n/a, published on 14 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain D-Link products are affected by: Buffer Overflow. This affects DIR-880L 1.08B04 and DIR-895 L/R 1.13b03. The impact is: execute arbitrary code (remote). The component is: htdocs/fileaccess.cgi. The attack vector is: A crafted HTTP request handled by fileacces.cgi could allow an attacker to mount a ROP attack: if the HTTP header field CONTENT_TYPE starts with ''boundary=' followed by more than 256 characters, a buffer overflow would be triggered, potentially causing code execution.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2017-14948?

It affects 6 products.


Products: Dlink Dir-868l Firmware, Dlink Dir-880l Firmware, Dlink Dir-885l Firmware, Dlink Dir-890l Firmware, Dlink Dir-895l Firmware, Dlink Dir-895r Firmware.

## How do I fix CVE-2017-14948?

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

## Is CVE-2017-14948 being exploited?

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

Public exploit code:

- CVE-2017-14948 for D-Link 880 Firmware (github_poc): https://github.com/badnack/d_link_880_bug

## Other vulnerabilities in n/a

- [CVE-2025-55583](https://insights.sbomify.com/CVE-2025-55583/): Command injection in n/a (critical 9.8)
- [CVE-2023-39665](https://insights.sbomify.com/CVE-2023-39665/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-39667](https://insights.sbomify.com/CVE-2023-39667/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-39668](https://insights.sbomify.com/CVE-2023-39668/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-29856](https://insights.sbomify.com/CVE-2023-29856/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14948 and fix it if it is affected.

What it is: CVE-2017-14948 is a critical memory corruption vulnerability in n/a, published on 14 Oct 2019. 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-2017-14948 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-2017-14948/ (Markdown: https://insights.sbomify.com/CVE-2017-14948/index.md)
```

## Sources

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

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