CVE-2003-0240
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 · uneditedThe web-based administration capability for various Axis Network Camera products allows remote attackers to bypass access restrictions and modify configuration via an HTTP request to the admin/admin.shtml containing a leading // (double slash).
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 confidenceAxis Network Camera web admin interface allows remote unauthenticated attackers to bypass access restrictions by requesting admin/admin.shtml with a leading double slash (//). This path traversal手法 enables attackers to modify device configuration without authentication.
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.32<= 2.32<= 2.32<= 2.32<= 2.32<= 2.32<= 2.32<= 3.00CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 device model and firmware versionAccess the Axis device web interface and navigate to the admin or settings page to view the firmware version, or query the device's built-in CGI endpoint (e.g., /axis-cgi/admin/param.cgi?action=list) to retrieve version informationAffected if The firmware version is at or below 2.32 for models 2100, 2110, 2120, 2130, 2400, 2401, 2420, or at or below 3.00 for model 2460
-
Confirm the web admin interface is accessible remotelyVerify whether the device's HTTP port (typically 80 or 8080) is listening on an IP address reachable from untrusted networksAffected if The admin interface is exposed to the internet or untrusted LAN segments without network segmentation
-
Test for the double-slash authentication bypassSend an HTTP GET request to //admin/admin.shtml (or /../../admin/admin.shtml) using curl or a browser, without providing any credentialsAffected if The request returns the admin configuration page or grants access to administrative functions without requiring authentication
-
Verify administrative actions are reachable without credentialsAfter confirming the bypass URL loads, attempt to modify a non-critical parameter (e.g., view system info or device name) through the accessible admin interfaceAffected if Administrative configuration changes can be made without any login prompt
A defender is affected if their Axis device model matches one of the affected versions and the web admin interface responds to the double-slash path bypass without requiring authentication.
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 firmware updates for affected Axis Network Camera models; if unavailable, restrict administrative interface access to trusted networks or disable remote admin access.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0240 — 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-2003-0240 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