dbcve.org
Flir Ax8 FirmwareOperating system · Flir

CVE-2023-51127

HIGH · 7.5 CVSS v3.1 Published 2024-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
FLIR AX8 thermal sensor cameras up to and including 1.46.16 are vulnerable to Directory Traversal due to improper access restriction. This vulnerability allows an unauthenticated, remote attacker to obtain arbitrary sensitive file contents by uploading a specially crafted symbolic link file. NOTE: The vendor has stated that with the introduction of firmware version 1.49.16 (Jan 2023) the FLIR AX8 should no longer be affected by the vulnerability reported. Latest firmware version (as of Oct 2025, was released Jun 2024) is 1.55.16.

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 confidence

FLIR AX8 thermal sensor cameras firmware up to version 1.46.16 contain a directory traversal vulnerability caused by improper access restrictions. An unauthenticated remote attacker can obtain arbitrary sensitive file contents by uploading specially crafted symbolic link files to the device.

MitigationUpgrade FLIR AX8 firmware to version 1.49.16 or later (vendor-stated fix), with 1.55.16 being the latest available version as of June 2024.

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
Flir Ax8 FirmwareOperating system
Affected:= 1.46.16

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the FLIR AX8 firmware version
    Access the device web interface or API and navigate to the firmware/version information page, typically found under Settings > Device Info or similar. Alternatively, check the response from common API endpoints like /api/device/info or /status
    Affected if The firmware version displayed is 1.46.16
  2. Verify the web management interface accessibility
    Attempt to reach the FLIR AX8 web interface from a browser using the device IP address (e.g., http://<device-ip>). Check if the login or status page loads without authentication
    Affected if The web interface is accessible without authentication and responds with the device login or status page
  3. Confirm file upload endpoint availability
    Check if the device exposes an upload functionality, typically through endpoints like /api/upload, /cgi-bin/upload, or similar file upload forms in the web interface. Attempt to access these endpoints or inspect the HTML source for file upload forms
    Affected if File upload endpoints are accessible without authentication or with default credentials
  4. Check network exposure of the device
    Review network firewall rules or access control lists to determine if the device web services (ports 80/443) are exposed to untrusted networks or the internet
    Affected if The device HTTP/HTTPS ports are reachable from untrusted network segments or the public internet

A user is affected if their FLIR AX8 device runs firmware version 1.46.16 and has its web interface or file upload functionality exposed to network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade FLIR AX8 firmware to version 1.49.16 or later (vendor-stated fix), with 1.55.16 being the latest available version as of June 2024.

Recommended fix High confidence

1.49.16 or later (recommended: 1.55.16)

  1. Obtain the firmware update file from the official FLIR support website or authorized distribution channel
  2. Access the FLIR AX8 device web interface or administrative panel
  3. Navigate to the firmware update or system settings section
  4. Upload the firmware file (version 1.49.16 or later, preferably 1.55.16)
  5. Follow the on-screen prompts to complete the firmware installation
  6. Verify the device is running the updated firmware version after reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flir Ax8 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-51127 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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