CVE-2009-2274
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 Huawei D100 allows remote attackers to obtain sensitive information via a direct request to (1) lan_status_adv.asp, (2) wlan_basic_cfg.asp, or (3) lancfg.asp in en/, related to use of JavaScript to protect against reading file contents.
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 Huawei D100 router has an information disclosure vulnerability where multiple ASP pages (lan_status_adv.asp, wlan_basic_cfg.asp, lancfg.asp in the en/ directory) leak sensitive configuration information. These pages attempt to protect content using client-side JavaScript, which can be bypassed by directly requesting the files, allowing unauthenticated remote attackers to obtain network configuration data.
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 dataall versionsCVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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.
-
Confirm Huawei D100 router modelCheck the device label, web interface header, or SNMP sysDescr for 'D100' identificationAffected if The device is a Huawei D100 router
-
Verify ASP pages are accessibleAttempt HTTP GET requests to /en/lan_status_adv.asp, /en/wlan_basic_cfg.asp, and /en/lancfg.asp without authenticationAffected if Any of these pages return HTTP 200 and contain configuration data
-
Check for information leakageInspect the HTTP response body from the ASP pages for sensitive values such as LAN IP ranges, wireless SSIDs, MAC addresses, or DHCP settingsAffected if The pages expose network configuration parameters without requiring authentication
-
Confirm client-side protection bypassDirectly request the ASP files (do not load in a browser with JavaScript enabled); verify the data is returned directly without any access controlAffected if Sensitive configuration data is returned without any login or session requirement
If you operate a Huawei D100 router and its ASP pages in the /en/ directory are accessible without authentication and return network configuration data, your environment is affected by CVE-2009-2274.
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 dataRestrict access to the router's administrative interface, disable remote WAN management or limit it to trusted IP addresses, and apply any available firmware updates from Huawei.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-2274 — 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-2009-2274 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