CVE-2018-25138
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 · uneditedFLIR AX8 Thermal Camera 1.32.16 contains hard-coded SSH and web panel credentials that cannot be changed through normal camera operations. Attackers can exploit these persistent credentials to gain unauthorized shell access and login to multiple camera interfaces using predefined username and password combinations.
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 · high confidenceThe FLIR AX8 Thermal Camera firmware version 1.32.16 contains hard-coded SSH and web panel credentials embedded in the firmware that cannot be changed through normal camera operations. Attackers with network access can use these predefined username and password combinations to gain unauthorized shell access and login to multiple camera interfaces.
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 data= 1.32.16= 1.17.13CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 modelCheck the device label, web interface, or system information to confirm the exact model is FLIR AX8 Thermal CameraAffected if The device is a FLIR AX8 model
-
Determine the installed firmware versionAccess the camera's web interface (usually via browser) and navigate to the System or About section to view the firmware version, or use the camera's administrative console if availableAffected if The firmware version is 1.32.16 or 1.17.13
-
Verify if SSH service is enabledCheck the camera's network settings or security configuration panel for SSH service status; attempt an outbound connection test to port 22 if the camera IP is knownAffected if SSH is enabled and accessible on the network
-
Verify if the web panel is enabledCheck the camera's web interface settings to confirm the web panel service is active; attempt to access the login page via HTTP/HTTPS to the camera's IP addressAffected if Web panel is enabled and reachable on the network
-
Attempt to change SSH or web credentialsThrough the camera's administrative interface, navigate to user management or credential settings and attempt to change the admin or root passwordAffected if Credentials cannot be changed or new accounts cannot be created/modified through the administrative interface
If the device is a FLIR AX8 running firmware 1.32.16 or 1.17.13 with SSH or web interfaces enabled, the hard-coded backdoor credentials are present and exploitable.
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 on a restricted network segment or behind firewalls to limit exposure, and contact FLIR for a firmware patch that removes the hardcoded credentials or allows credential changes.
- Consultation6.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,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25138 — 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-25138 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