CVE-2005-3490
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 · uneditedDirectory traversal vulnerability in the web server in Asus Video Security 3.5.0.0 and earlier allows remote attackers to read arbitrary files via "../" or "..\" sequences in the URL.
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 confidenceDirectory traversal vulnerability in the web server of Asus Video Security 3.5.0.0 and earlier allows remote attackers to read arbitrary files on the host system by using '../' or '..\' sequences in crafted URLs.
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<= 3.5.0.0CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 if Asus Video Security is installedCheck common installation paths such as C:\Program Files\ASUS\VideoSecurity or look for the application in Add/Remove Programs. Also check for processes named VideoSecurity.exe or similar.Affected if The software is found on the system
-
Determine the installed versionRight-click the executable (typically VideoSecurity.exe) in the installation folder, select Properties, and check the Version tab. Alternatively, check Add/Remove Programs for the version number.Affected if The version is 3.5.0.0 or earlier
-
Verify the web server component is runningCheck if the application is running and listening on common HTTP ports (typically port 8080 or 80). Use command: netstat -an | findstr LISTENING to identify open ports associated with the application.Affected if The web server component is active and accepting connections
-
Confirm the directory traversal vulnerability is exploitableAttempt to access a known file outside the web root using a traversal sequence. For example, request a URL like http://target:port/..\..\windows\system32\config\sam or http://target:port/../../boot.ini using a web browser or curl command.Affected if The server returns content from files outside the intended web root directory
If Asus Video Security Online version 3.5.0.0 or earlier is installed with the web server enabled, and directory traversal requests return arbitrary file contents, the system is affected by CVE-2005-3490.
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 dataUpgrade to a patched version of Asus Video Security; if the product is end-of-life, replace with a current, supported video security solution and implement network segmentation to limit exposure.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3490 — 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-2005-3490 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