CVE-2025-2002
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 · uneditedCWE-532: Insertion of Sensitive Information into Log Files vulnerability exists that could cause the disclosure of FTP server credentials when the FTP server is deployed, and the device is placed in debug mode by an administrative user and the debug files are exported from the device.
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 confidenceThis vulnerability allows FTP server credentials to be written to debug log files when debug mode is enabled on a device with a deployed FTP server. When an administrative user places the device in debug mode and exports the debug files, the credentials stored for the FTP server are disclosed in the logs due to insufficient sanitization of sensitive information in debug output.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/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 FTP server is deployedCheck device configuration for FTP server settings, or look for FTP service listening on port 21Affected if FTP server is configured and running on the device
-
Verify if debug mode is enabledCheck device administrative interface or configuration files for debug/logging mode settingsAffected if Debug mode is currently enabled on the device
-
Locate debug log filesSearch standard debug log directories on the device for recently modified log files, especially those generated after debug mode was activatedAffected if Debug log files exist and were created during debug mode sessions
-
Search debug logs for FTP credentialsGrep or search debug log files for strings matching FTP username, password, or authentication fields (e.g., patterns like 'ftp', 'pass', credentials in plain text)Affected if Debug logs contain FTP server credentials in plain text
-
Check for exported debug filesReview any exported or downloaded debug bundles from the deviceAffected if Debug files were exported externally while FTP server credentials were configured
The environment is affected if FTP server credentials can be found in debug log files or exported debug bundles, which occurs when debug mode is enabled on a device with a deployed FTP server.
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 dataAvoid enabling debug mode on devices with deployed FTP servers. If debugging is required, ensure debug files are protected with access controls and not exported unless absolutely necessary. Consider implementing credential masking in all debug logging paths.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2002 — 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-2025-2002 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