CVE-2002-2356
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 · uneditedHAMweather 2.x allows remote attackers to modify administrative settings and obtain sensitive information via a direct request to hwadmin.cgi.
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 confidenceHAMweather 2.x contains an authentication bypass vulnerability in the hwadmin.cgi administrative script. The script can be accessed directly without proper authentication, allowing remote attackers to modify administrative settings and retrieve sensitive information by issuing direct HTTP requests to the admin interface.
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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Locate the hwadmin.cgi scriptSearch the web server document root for the hwadmin.cgi file, typically in the /cgi-bin/ or same directory as the main HAMweather installationAffected if The file exists on the server
-
Verify direct HTTP access to hwadmin.cgiSend an HTTP GET request to the hwadmin.cgi URL (for example, http://yourserver.com/cgi-bin/hwadmin.cgi) without providing any authentication credentials or session cookiesAffected if The script responds with administrative functionality or login prompts without requiring authentication
-
Check for web server access controlsExamine the web server configuration (such as .htaccess files or Apache config) for any rules restricting access to hwadmin.cgiAffected if No access restrictions are configured for hwadmin.cgi, or the script ignores such restrictions
-
Inspect admin functionality without credentialsIf hwadmin.cgi responds, attempt to access administrative features (such as viewing settings or configuration pages) by issuing direct HTTP requests to the scriptAffected if Administrative features are accessible without any form of authentication
If hwadmin.cgi exists and responds to direct HTTP requests without requiring any authentication, the environment is affected by this vulnerability.
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 hwadmin.cgi through web server authentication (e.g., .htaccess, IP restrictions) or implement proper session-based authentication within the script itself. If the product is no longer supported, consider migrating to a maintained weather software solution.
- Consultation2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2356 — 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-2002-2356 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