CVE-2023-46295
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 · uneditedAn issue was discovered in Teledyne FLIR M300 2.00-19. Unauthenticated remote code execution can occur in the web server. An attacker can exploit this by sending a POST request to the vulnerable PHP page. An attacker can elevate to root permissions with Sudo.
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 confidenceUnauthenticated remote code execution vulnerability in Teledyne FLIR M300 camera web server (firmware 2.00-19). Attackers can achieve RCE by sending a POST request to a vulnerable PHP page and can escalate to root privileges using Sudo.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- 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 camera modelAccess the camera's web interface or check the device inventory to confirm the exact model is Teledyne FLIR M300Affected if The device is a Teledyne FLIR M300 camera
-
Check the firmware versionLog into the camera's admin interface or use the vendor's management tool to retrieve the current firmware version. Compare against the affected range: firmware 2.00-19Affected if The installed firmware version is 2.00-19 or lower
-
Verify the web server is accessibleAttempt to access the camera's web interface over HTTP/HTTPS from the network segment where the camera is deployedAffected if The web server responds to HTTP/HTTPS requests on the network
-
Identify the PHP endpoint exposureSend a POST request to common PHP paths on the camera's web server (e.g., /admin/*.php, /cgi-bin/*.php) to check for vulnerable endpoints. Use a tool like curl or Burp Suite to inspect responsesAffected if The vulnerable PHP page accepts unauthenticated POST requests and returns unexpected behavior or executes commands
-
Check network exposureReview firewall rules, access control lists, and network segmentation to determine if the camera's web interface is accessible from untrusted networks or the internetAffected if The camera web server is accessible from untrusted network segments or the public internet
-
Review Sudo configurationIf the camera is compromised, check the sudoers configuration on the device for any misconfigurations that allow the web server user to execute commands as rootAffected if The web server process user has improper sudo privileges allowing root command execution
The environment is affected if it contains a Teledyne FLIR M300 camera running firmware version 2.00-19 or lower with the web server exposed to network access.
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 dataRestrict network access to the camera, apply vendor firmware update when available, or implement web application firewall rules to block malicious requests to the vulnerable endpoint.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46295 — 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-2023-46295 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