# CVE-2018-3813: Information disclosure in n/a

> An attacker can read sensitive user credentials from FLIR Brickstream 2300 devices by accessing a specific CGI endpoint without authentication.

- **Severity:** Critical 9.8 (`CVSS:3.0/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 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2h46-qm7g-f6ww

## What is CVE-2018-3813?

CVE-2018-3813 is a critical vulnerability in n/a, published on 1 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

getConfigExportFile.cgi on FLIR Brickstream 2300 devices 2.0 4.1.53.166 has Incorrect Access Control, as demonstrated by reading the AVI_USER_ID and AVI_USER_PASSWORD fields via a direct request.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 3 products.


Products: Flir Brickstream 2300 2d Firmware, Flir Brickstream 2300 3d\+ Firmware, Flir Brickstream 2300 3d Firmware.

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

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

## Is CVE-2018-3813 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3813 is a critical vulnerability in n/a, published on 1 Jan 2018. 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-2018-3813 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-2018-3813/ (Markdown: https://insights.sbomify.com/CVE-2018-3813/index.md)
```

## Sources

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

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