CVE-2024-6509
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 · uneditedMarinus Pfund, member of the AXIS OS Bug Bounty Program, has found the VAPIX API alwaysmulti.cgi was vulnerable for file globbing which could lead to resource exhaustion of the Axis device. Axis has released patched AXIS OS versions for the highlighted flaw. Please refer to the Axis security advisory for more information and solution.
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 confidenceThe VAPIX API alwaysmulti.cgi script in AXIS OS devices is vulnerable to file globbing, which allows an attacker to cause excessive file system operations leading to resource exhaustion and potential denial of service on the device.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 AXIS OS device and firmware versionAccess the device web interface or use the VAPIX API to query the /axis-cgi/debug/debug.cgi endpoint or check the system firmware version via the device's administrative interface. The firmware version is typically displayed under Settings > About or System > Overview.Affected if The device runs an unpatched AXIS OS version that falls within the affected range documented in the Axis security advisory for CVE-2024-6509.
-
Verify VAPIX API is enabledAttempt to access the VAPIX API by sending an HTTP request to the device's IP address on port 80 or 443. For example, send a GET request to http://<device_ip>/axis-cgi/jws.cgi or test connectivity to the /vapix/ endpoint. If the API responds, it is enabled.Affected if The VAPIX API is exposed and accessible on the network, making the alwaysmulti.cgi script reachable.
-
Confirm alwaysmulti.cgi endpoint is accessibleSend an HTTP GET request to http://<device_ip>/axis-cgi/alwaysmulti.cgi and observe the response. A valid response (even an error) indicates the endpoint exists and can be reached.Affected if The alwaysmulti.cgi script is accessible, which is required for the file globbing vulnerability to be exploitable.
-
Check for signs of resource exhaustionMonitor the device CPU, memory, and disk I/O during or after repeated requests to alwaysmulti.cgi. Use the device's built-in diagnostics or external monitoring to observe if file system operations spike abnormally.Affected if The device exhibits unusually high file system activity or resource consumption in response to requests targeting alwaysmulti.cgi, indicating active exploitation or susceptibility to the globbing attack.
A user is affected if they have an AXIS OS device with an unpatched firmware version, the VAPIX API is exposed, and the alwaysmulti.cgi endpoint is accessible, allowing file globbing to cause excessive file system operations.
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 the patched AXIS OS versions provided in the Axis security advisory to affected devices. Identify all exposed VAPIX API endpoints and implement rate limiting or access controls as a compensating control until patching is complete.
- Consultation4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6509 — 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-2024-6509 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