CVE-2018-12920
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBrickstream 2300 devices allow remote attackers to obtain potentially sensitive information via a direct request for the basic.html#ipsettings or basic.html#datadelivery URI.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Brickstream 2300 video analytics device exposes a web interface where sensitive configuration data (IP settings, data delivery parameters) can be retrieved by remote unauthenticated attackers via direct requests to basic.html#ipsettings or basic.html#datadelivery URIs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the web interface and look for Brickstream 2300 identification in the login page, header, or device information section. Alternatively, check DHCP fingerprints, MAC vendor prefix (FLIR Systems), or network documentation for this device.Affected if The device is a Flir Brickstream 2300 video analytics device
-
Confirm web interface accessibilityAttempt to reach the device's IP address on HTTP/HTTPS ports (typically 80/443) from a network location that should not have access, such as an external IP or an untrusted VLAN. Verify the basic.html page loads.Affected if The web interface is reachable from untrusted networks without VPN or firewall restrictions
-
Test unauthenticated access to ipsettingsDirect your browser to http://[device-ip]/basic.html#ipsettings or https://[device-ip]/basic.html#ipsettings without providing any login credentials. Inspect whether IP configuration data (addresses, subnet, gateway) is displayed.Affected if The ipsettings URI returns configuration data without requiring authentication
-
Test unauthenticated access to datadeliveryNavigate to http://[device-ip]/basic.html#datadelivery or https://[device-ip]/basic.html#datadelivery without logging in. Check whether data delivery parameters (destinations, ports, protocols) are exposed.Affected if The datadelivery URI returns configuration data without requiring authentication
-
Verify no authentication is required on base pageLoad the root URL of the device (such as / or /basic.html) and confirm no login prompt appears or authentication is not enforced before viewing configuration sections.Affected if The web interface allows access to configuration URIs without any authentication token or session
If the Flir Brickstream 2300 web interface is accessible from untrusted networks and the basic.html#ipsettings or basic.html#datadelivery URIs return sensitive configuration data without requiring authentication, the environment is affected by CVE-2018-12920.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataIsolate affected devices behind a firewall or VPN to limit exposure, contact vendor for firmware/security patch, and disable remote web interface access if not operationally required.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12920 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-12920 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data