# CVE-2019-13991: Other in n/a

> Remote attackers can manipulate LED states on Arduino systems via laser-induced photosensitivity, affecting embedded device integrity.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-589h-8jj7-3j6m

## What is CVE-2019-13991?

CVE-2019-13991 is a medium-severity vulnerability in n/a, published on 19 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Embedded systems based on Arduino before Rev3 allow remote attackers to send data to LEDs (directly connected to GPIO pins) via a laser, because of LED photosensitivity.

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

It affects 1 product.


Products: Arduino Arduino Firmware.

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

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

## Is CVE-2019-13991 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13991 is a medium-severity vulnerability in n/a, published on 19 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13991 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-13991/ (Markdown: https://insights.sbomify.com/CVE-2019-13991/index.md)
```

## Sources

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

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