CVE-2002-1047
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 FTP service in Watchguard Soho Firewall 5.0.35a allows remote attackers to gain privileges with a correct password but an incorrect user name.
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 FTP service in Watchguard SOHO Firewall 5.0.35a contains an authentication bypass vulnerability where the system validates the password but fails to properly validate the username, allowing remote attackers to gain elevated privileges using a correct password with an incorrect username.
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= 5.0.35aCVSS 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.
-
Identify the firewall deviceDetermine if the target system is a Watchguard SOHO Firewall device. This is typically visible in the device label, management interface, or network identification.Affected if The device is a Watchguard SOHO Firewall
-
Check the firmware versionAccess the Watchguard SOHO Firewall management interface or use the device's version check command to confirm the installed firmware version is 5.0.35a.Affected if The firmware version is exactly 5.0.35a
-
Verify FTP service statusCheck if the FTP service is enabled and running on the Watchguard SOHO Firewall. This can be done through the management interface under services or by attempting a connection to the FTP port (port 21).Affected if The FTP service is enabled and accessible on the network
-
Test authentication behavior (if authorized)If you have authorization, attempt an FTP login using any incorrect username together with a known correct password configured on the system. Observe whether access is granted despite the incorrect username.Affected if Login succeeds with an incorrect username but correct password, indicating the authentication bypass is present
The environment is affected if it is a Watchguard SOHO Firewall running firmware version 5.0.35a with the FTP service enabled and the authentication bypass vulnerability is present.
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 dataApply the vendor-provided patch or update to Watchguard SOHO Firewall 5.0.35a. If no patch is available, disable the FTP service until a fix can be applied, or implement additional network-level access controls to limit FTP exposure.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1047 — 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-1047 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