dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 13 Jun 2022.
Windows 10 1507Operating system · Microsoft

CVE-2019-0703

MEDIUM · 6.5 CVSS v3.1 Published 2019-04-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable Zero-click Patch available

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 · unedited
An information disclosure vulnerability exists in the way that the Windows SMB Server handles certain requests, aka 'Windows SMB Information Disclosure Vulnerability'. This CVE ID is unique from CVE-2019-0704, CVE-2019-0821.

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 confidence

This is an information disclosure vulnerability in Windows SMB Server. The vulnerability exists in how the SMB Server handles certain requests, potentially allowing an authenticated attacker to obtain sensitive information from the server. The flaw allows information leakage without requiring code execution.

MitigationApply the appropriate Microsoft security updates for Windows SMB Server. If immediate patching is not possible, consider restricting SMB access through firewalls or disabling SMBv1 where not required.

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
Windows 10 1507Operating system
Affected:all versions
Windows 10 1607Operating system
Affected:all versions
Windows 10 1703Operating system
Affected:all versions
Windows 10 1709Operating system
Affected:all versions
Windows 10 1803Operating system
Affected:all versions
Windows 10 1809Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows version
    Affected if The version matches Windows 10 1507, 1607, 1703, 1709, 1803, 1809, Windows 7, or Windows 8.1 (all versions of these releases)
  2. Verify SMB Server is enabled
    Check if the SMB Server service (LanmanServer) is running: run 'Get-Service LanmanServer' in PowerShell or check Services.msc for 'Server' service
    Affected if The SMB Server service is running and accepting SMB connections
  3. Confirm SMB exposure
    Check if SMB ports (445 or 139) are listening: run 'netstat -an | findstr ":445"' or use PowerShell 'Get-NetTCPConnection -LocalPort 445 -State Listen'
    Affected if SMB ports are open and accepting connections on the system
  4. Check for security updates
    Query installed updates: run 'Get-HotFix | Select-Object HotFixID, InstalledOn' or view Windows Update history for security updates related to SMB
    Affected if The specific security update for CVE-2019-0703 is not installed (note: specific KB number would need to be verified against Microsoft documentation)

A system is affected if it runs an unpatched Windows 10 1507-1809, Windows 7, or Windows 8.1 version with SMB Server enabled and exposed on the network

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Apply the appropriate Microsoft security updates for Windows SMB Server. If immediate patching is not possible, consider restricting SMB access through firewalls or disabling SMBv1 where not required.

Recommended fix Moderate confidence

Apply the Microsoft security update released for this vulnerability (refer to MSRC for the specific KB article number for your Windows version)

  1. Verify the current Windows version by running 'winver' in the Run dialog
  2. Open Windows Update Settings (Settings > Update & Security > Windows Update)
  3. Click 'Check for updates' to install all available security updates
  4. Confirm that the specific security update for CVE-2019-0703 is installed by viewing the update history
  5. For Windows 7 and Windows 8.1, ensure Extended Security Updates (ESU) are purchased and configured if support has ended
  6. Alternatively, manually download the specific security update from the Microsoft Update Catalog by searching for 'CVE-2019-0703'
Caveat Windows 7 and Windows 8.1 require Extended Security Updates (ESU) purchased separately after end of support; some older Windows 10 versions (1507, 1607) are also out of support

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0703 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0703 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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