# CVE-2023-46295: Server-side request forgery in n/a

> Unauthenticated attackers can achieve remote code execution and root privileges via SSRF in the web server of Teledyne FLIR M300 devices.

- **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:** 1 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-7gx3-fr27-7gx9

## What is CVE-2023-46295?

CVE-2023-46295 is a critical server-side request forgery vulnerability in n/a, published on 1 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Teledyne FLIR M300 2.00-19. Unauthenticated remote code execution can occur in the web server. An attacker can exploit this by sending a POST request to the vulnerable PHP page. An attacker can elevate to root permissions with Sudo.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2023-46295?


## How do I fix CVE-2023-46295?

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

## Is CVE-2023-46295 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46295 and fix it if it is affected.

What it is: CVE-2023-46295 is a critical server-side request forgery vulnerability in n/a, published on 1 May 2024. 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-2023-46295 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-2023-46295/ (Markdown: https://insights.sbomify.com/CVE-2023-46295/index.md)
```

## Sources

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

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