700 Network Document ServerHardware / appliance · Axis

CVE-2000-0144

HIGH · 7.5 CVSS v2.0 Published 2000-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Axis 700 Network Scanner does not properly restrict access to administrator URLs, which allows users to bypass the password protection via a .. (dot dot) attack.

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 confidence

The Axis 700 Network Scanner fails to properly sanitize path inputs in administrator URLs, allowing remote attackers to bypass authentication through directory traversal (..) sequences to access protected administrative functions without valid credentials.

MitigationImplement proper input validation and path sanitization for all URL parameters to reject directory traversal sequences. If vendor patches are unavailable, restrict administrative interface access to trusted networks via firewall rules or VPN.

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
700 Network Document ServerHardware / appliance
Affected:= 1.0= 1.10= 1.11= 1.12= 1.13= 1.14

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Identify if Axis 700 is accessible on the network
    Scan network for devices responding on common HTTP ports (80, 8080) and check for Axis 700 Network Scanner/Document Server in service banners or web interface title
    Affected if Axis 700 Network Scanner or Document Server is found responding on the network
  2. Determine the installed version
    Access the device web interface and navigate to the About or System Information page, or query the HTTP server banner for version information
    Affected if The version is 1.0, 1.10, 1.11, 1.12, 1.13, or 1.14
  3. Verify administrative interface is exposed
    Attempt to access the administrative URL paths such as /admin/, /scanner/admin/, or / administrator endpoints without authentication
    Affected if Administrative interface or authentication prompts are reachable without credentials
  4. Test for directory traversal vulnerability
    Send HTTP GET requests to administrative URLs containing ../ sequences (e.g., /admin/../../etc/passwd or similar path manipulation) and observe if the response differs from expected access denied messages
    Affected if Directory traversal sequences return content that should require authentication or reveal file contents outside the web root

A system is affected if an Axis 700 Network Scanner/Document Server versions 1.0-1.14 is running with its administrative interface accessible and responds to directory traversal sequences by bypassing authentication controls.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and path sanitization for all URL parameters to reject directory traversal sequences. If vendor patches are unavailable, restrict administrative interface access to trusted networks via firewall rules or VPN.

Fix this in 700 Network Document Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2000-0144 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2000-0144 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