CVE-2002-0310
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 · uneditedNetwin WebNews 1.1k CGI program includes several default usernames and cleartext passwords that cannot be deleted by the administrator, which allows remote attackers to gain privileges via the username/password combinations (1) testweb/newstest, (2) alwn3845/imaptest, (3) alwi3845/wtest3452, or (4) testweb2/wtest4879.
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 confidenceNetwin WebNews 1.1k CGI program contains hardcoded default credentials (testweb/newstest, alwn3845/imaptest, alwi3845/wtest3452, testweb2/wtest4879) stored in cleartext that cannot be removed by administrators, allowing remote unauthenticated attackers to gain elevated privileges.
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= 1.1h= 1.1i= 1.1j= 1.1kCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WebNews is runningCheck running processes for 'webnews' or inspect the web server configuration to see if the WebNews CGI (typically webnews.exe or webnews.cgi) is being servedAffected if WebNews CGI is accessible on the system
-
Identify WebNews versionLocate the WebNews executable or CGI file and query its version information, or access the application's login page and check any version disclosure in headers or the interfaceAffected if Version is 1.1h, 1.1i, 1.1j, or 1.1k
-
Inspect user account configurationExamine the WebNews configuration files or user database for accounts named testweb, alwn3845, alwi3845, or testweb2Affected if Any of these hardcoded accounts (testweb, alwn3845, alwi3845, testweb2) exist and are active in the WebNews user store
-
Test hardcoded credentialsAttempt to authenticate to WebNews using each default credential pair: testweb/newstest, alwn3845/imaptest, alwi3845/wtest3452, testweb2/wtest4879Affected if Any of these credential pairs successfully authenticate
You are affected if WebNews version 1.1h-1.1k is running AND the hardcoded accounts testweb, alwn3845, alwi3845, or testweb2 are present and allow authentication with their default passwords.
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 dataIf a vendor patch exists, apply it immediately. Otherwise, disable or restrict access to the WebNews service, implement network-level access controls, or migrate to a supported alternative solution.
- Consultation3.0 h
- Implementation5.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 $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0310 — 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-0310 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