CVE-2025-58107
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 · uneditedIn Microsoft Exchange through 2019, Exchange ActiveSync (EAS) configurations on on-premises servers may transmit sensitive data from Samsung mobile devices in cleartext, including the user's name, e-mail address, device ID, bearer token, and base64-encoded password.
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 confidenceMicrosoft Exchange on-premises servers with Exchange ActiveSync (EAS) configurations transmit sensitive Samsung mobile device data (user names, email addresses, device IDs, bearer tokens, and base64-encoded passwords) in cleartext rather than encrypted form. An attacker with network positioning could intercept this traffic to harvest credentials and device identifiers.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm Exchange Server and EAS are presentRun 'Get-ExchangeServer | Select-Object Name,AdminDisplayVersion' to identify Exchange installations, then run 'Get-ActiveSyncVirtualDirectory -Server <servername> | Select-Object Name,InternalUrl,ExternalUrl' to check if EAS virtual directories exist.Affected if Exchange Server is installed and Exchange ActiveSync virtual directories are configured.
-
Verify EAS SSL/TLS configurationIn Exchange Management Shell, run 'Get-ActiveSyncVirtualDirectory -Server <servername> | Select-Object Name,SSLAccessRequired,ClientCertAuth' to check if SSL is required for EAS connections.Affected if SSLAccessRequired is set to False or ClientCertAuth is set to Ignore, indicating unencrypted connections are allowed.
-
Inspect IIS EAS virtual directory SSL settingsOpen IIS Manager, navigate to the Microsoft-Server-ActiveSync virtual directory under Default Web Site, click SSL Settings, and verify 'Require SSL' is unchecked or not enforced.Affected if Require SSL is unchecked for the Microsoft-Server-ActiveSync virtual directory.
-
Check EAS mailbox user partnershipsRun 'Get-CASMailbox -Identity <user> | Select-Object ActiveSyncEnabled,ActiveSyncMailboxPolicy' to identify which mailboxes have EAS enabled, then run 'Get-MobileDevice -Mailbox <user> | Select-Object DeviceType,DeviceModel' to see if Samsung devices are syncing.Affected if ActiveSyncEnabled is True for mailboxes with Samsung (or generic Android/iOS) devices present in mobile device partnerships.
-
Capture network traffic to verify cleartext transmissionUse a packet capture tool (such as Wireshark or netsh trace) on the Exchange server network interface to capture traffic on ports 80/443 and inspect if EAS traffic to/from mobile devices contains readable username, email, or base64-encoded credential data.Affected if Plaintext HTTP traffic on port 80 is observed containing EAS XML payloads with sensitive Samsung device synchronization data.
If Exchange Server has EAS enabled and configured without requiring SSL/TLS (or allowing port 80 connections), the sensitive Samsung device data is being transmitted in cleartext and the environment is affected.
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 dataConfigure EAS to require TLS encryption for all connections, and review Samsung device policies to ensure encryption is enforced during synchronization with Exchange servers.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58107 — 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-58107 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