dbcve.org
Flir Ax8 FirmwareOperating system · Flir

CVE-2024-3013

HIGH · 8.8 CVSS v3.1 Published 2024-03-28
Fix available
A fix is available. Upgrade to after 1.46.16 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A flaw has been found in Teledyne FLIR AX8 up to 1.46.16. The impacted element is an unknown function of the file /tools/test_login.php?action=register of the component User Registration. Executing manipulation can lead to improper authorization. The attack may be performed from remote. The exploit has been published and may be used. Upgrading to version 1.49.16 is sufficient to resolve this issue. Upgrading the affected component is recommended. The vendor points out: "FLIR AX8 internal web site has been refactored to be able to handle the reported vulnerabilities."

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

The FLIR AX8 thermal camera's web interface contains an improper authorization vulnerability in the user registration endpoint (/tools/test_login.php?action=register). This allows remote unauthenticated attackers to register new administrative users on the device, bypassing proper access controls.

MitigationUpgrade FLIR AX8 firmware to version 1.49.16 or later to resolve the authorization bypass in the user registration component.

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.0, <= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Check firmware version
    Access the FLIR AX8 web interface and navigate to System > About or Settings > Firmware to view the installed version. Alternatively, query the device API or check the system information page.
    Affected if The firmware version is between 1.46.0 and 1.46.16 inclusive (versions outside this range are not affected)
  2. Confirm web interface is running
    Attempt to access the FLIR AX8 device IP address via HTTP in a web browser or use a tool like curl to verify the web service is responding.
    Affected if The web interface is accessible on the network
  3. Inspect registered user accounts
    Log into the device administration panel and review the user management section to enumerate all registered accounts, looking for unauthorized or unexpected administrative users.
    Affected if Unknown administrative user accounts exist that were not created by legitimate administrators
  4. Test the registration endpoint
    Send an HTTP request to /tools/test_login.php?action=register on the device to verify if the endpoint responds and accepts unauthenticated registration attempts.
    Affected if The endpoint responds and allows registration without authentication

A FLIR AX8 device is affected if it runs firmware version 1.46.0 through 1.46.16 and has its web interface accessible, enabling the unauthorized admin user registration vulnerability.

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
Upgrade available Upgrade to a release after 1.46.16
Interim mitigation

Upgrade FLIR AX8 firmware to version 1.49.16 or later to resolve the authorization bypass in the user registration component.

Recommended fix High confidence

1.49.16

  1. Download the FLIR AX8 firmware version 1.49.16 from the official Teledyne FLIR support website
  2. Access the FLIR AX8 web interface or management console
  3. Navigate to the firmware update or system settings section
  4. Upload the version 1.49.16 firmware file
  5. Confirm the firmware installation and allow the device to reboot
  6. Verify the device is running version 1.49.16 after the reboot

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

Fix this in Flir Ax8 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3013 — 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-2024-3013 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