CVE-2023-21410
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 · uneditedUser provided input is not sanitized on the AXIS License Plate Verifier specific “api.cgi” allowing for arbitrary code execution.
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 confidenceCommand injection vulnerability in AXIS License Plate Verifier's api.cgi endpoint where unsanitized user input is passed to system shell, enabling arbitrary code execution with the privileges of the web service.
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<= 2.8.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Axis License Plate VerifierAccess the device web interface and navigate to the System > About or Settings > Basic Setup > About section to view the software version. Alternatively, check via the device's SNMP interface or firmware check utility if available.Affected if The displayed version is 2.8.3 or lower.
-
Confirm the api.cgi endpoint is accessibleAttempt to access the api.cgi endpoint on the device (typically at /axis-cgi/verifier/api.cgi or similar path under the device's web root). Check if the endpoint responds to HTTP requests.Affected if The api.cgi endpoint is reachable from the network and accepts requests without authentication restrictions.
-
Verify web service privilege levelReview the device documentation or check the process running the web service (typically apache, lighttpd, or Axis own web server) to determine under which user account it executes.Affected if The web service runs as root or a privileged user account rather than a restricted service account.
-
Inspect network exposure of the deviceReview firewall rules, networkACLs, or VLAN configuration to determine if the device management interface and api.cgi are accessible from untrusted networks.Affected if The device management interface with api.cgi is exposed to the internet or untrusted LAN segments.
-
Check for signs of exploitation or unauthorized accessReview device logs (System > Logs) for unusual commands, unexpected system calls, or authentication anomalies around the api.cgi endpoint.Affected if Logs show unexpected shell commands, suspicious input patterns, or unauthorized access attempts to api.cgi.
The environment is affected if Axis License Plate Verifier version 2.8.3 or lower is installed and the api.cgi endpoint is network-accessible, since the command injection can be triggered by unsanitized input to this endpoint.
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 dataApply vendor patch when available; implement strict input validation on api.cgi; restrict network access to the device.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21410 — 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-21410 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