# CVE-2019-13193: Memory corruption in n/a

> A stack buffer overflow in Brother printer web servers allows attackers to execute arbitrary code on the device.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w49w-3g45-4f86

## What is CVE-2019-13193?

CVE-2019-13193 is a high-severity memory corruption vulnerability in n/a, published on 13 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Some Brother printers (such as the HL-L8360CDW v1.20) were affected by a stack buffer overflow vulnerability as the web server did not parse the cookie value properly. This would allow an attacker to execute arbitrary code on the device.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 300 products.


Products: Brother Ads-2400n Firmware, Brother Ads-2800w Firmware, Brother Ads-3000n Firmware, Brother Ads-3600w Firmware, Brother Dcp-1610w Firmware, Brother Dcp-1610we Firmware, Brother Dcp-1610wr Firmware, Brother Dcp-1610wvb Firmware, Brother Dcp-1612w Firmware, Brother Dcp-1612we Firmware, Brother Dcp-1612wr Firmware, Brother Dcp-1612wvb Firmware, Brother Dcp-1615nw Firmware, Brother Dcp-1616nw Firmware, Brother Dcp-1617nw Firmware, Brother Dcp-1618w Firmware, Brother Dcp-1622we Firmware, Brother Dcp-1623we Firmware, Brother Dcp-1623wr Firmware, Brother Dcp-7180dn Firmware and 280 more.

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

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

## Is CVE-2019-13193 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13192](https://insights.sbomify.com/CVE-2019-13192/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-13194](https://insights.sbomify.com/CVE-2019-13194/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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