CVE-2025-25002
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 · uneditedInsertion of sensitive information into log file in Azure Local Cluster allows an authorized attacker to disclose information over an adjacent network.
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 confidenceAzure Local Cluster contains a vulnerability where sensitive information is being written to log files, which can be accessed by an authorized attacker over an adjacent network. This is an information disclosure vulnerability stemming from improper handling of sensitive data in logging operations.
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< 2411.2CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/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 Azure Local Cluster installationUse the Azure Local management interface or system inventory tools to confirm the presence of Microsoft Azure Local Cluster and retrieve its installed version numberAffected if Azure Local Cluster is installed and the version is lower than 2411.2
-
Compare version against affected rangeLocate the installed version number and verify it falls below 2411.2 (for example, 2411.1, 2410.x, or earlier)Affected if The installed version is anything less than 2411.2
-
Locate log file directoriesAccess the file system on the Azure Local Cluster node and navigate to the default log directories used by Azure Local Cluster componentsAffected if Log directories exist and contain log files from Azure Local Cluster services
-
Inspect log files for sensitive dataOpen recent log files and search for patterns indicating sensitive information such as passwords, keys, tokens, secrets, or credentials in plain textAffected if Log files contain readable sensitive data such as authentication credentials, API keys, or other secrets
-
Check log file access controlsReview file permissions on log directories and files to determine if adjacent network attackers with authorized access could read themAffected if Log files have permissions that allow an authorized attacker on the adjacent network to read them
You are affected if Azure Local Cluster version is below 2411.2 and log files contain exposed sensitive information accessible from the adjacent network.
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 data2411.2
Review and sanitize all logging operations in Azure Local Cluster to prevent sensitive information from being written to log files. Implement proper access controls on log files and consider encrypting sensitive data before logging.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25002 — 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-25002 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