# CVE-2018-25137: FLIR Brickstream 3D+ 2.1.742.1842 Unauthenticated Config File Disclosure

> Unauthenticated attackers can download sensitive configuration files via the ExportConfig REST API, potentially leading to authentication bypass and privilege escalation.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** GHSA-8hvh-73q5-g7pg

## What is CVE-2018-25137?

CVE-2018-25137 is a high-severity vulnerability in FLIR Brickstream 3D+, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FLIR Brickstream 3D+ 2.1.742.1842 contains an unauthenticated vulnerability in the ExportConfig REST API that allows attackers to download sensitive configuration files. Attackers can exploit the getConfigExportFile.cgi endpoint to retrieve system configurations, potentially enabling authentication bypass and privilege escalation.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2018-25137 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25137 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25137 is a high-severity vulnerability in FLIR Brickstream 3D+, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25137 exists.

Affected product: FLIR Brickstream 3D+. 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-2018-25137/ (Markdown: https://insights.sbomify.com/CVE-2018-25137/index.md)
```

## Sources

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

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