CVE-2019-18381
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 · uneditedNorton Password Manager, prior to 6.6.2.5, may be susceptible to a cross origin resource sharing (CORS) vulnerability, which is a type of issue that allows restricted resources on a web page to be requested from another domain outside the domain from which the first resource was served.
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 confidenceNorton Password Manager versions prior to 6.6.2.5 contain a CORS misconfiguration that allows cross-origin requests from arbitrary domains. This could enable a malicious website to make requests to the password manager's web resources and potentially exfiltrate sensitive data such as stored credentials.
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< 6.6.2.5CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 Norton Password Manager versionOpen Norton Password Manager (browser extension or desktop app) and navigate to the About or Settings section to view the installed version number. Alternatively, check the extensions management page in your browser for Norton Password Manager version info.Affected if The displayed version is earlier than 6.6.2.5 (e.g., 6.6.0.0, 6.5.x, etc.)
-
Access the web vault interfaceLog in to the Norton Password Manager web vault if available (typically accessed through the browser extension or Norton account).Affected if The web vault interface is accessible and responds to requests
-
Inspect CORS response headersUse browser developer tools (Network tab) or a command-line tool like curl to make a cross-origin request to the Norton Password Manager web resources. Examine the Access-Control-Allow-Origin header in the response.Affected if The Access-Control-Allow-Origin header is set to '*' (wildcard) or allows arbitrary domains rather than restricting to specific trusted origins
-
Check for CORS misconfiguration in browser consoleOpen browser console on a page hosting Norton Password Manager and attempt a fetch/XMLHttpRequest to the password manager domain from a different origin. Look for any successful responses that should have been blocked.Affected if Cross-origin requests succeed without proper origin validation, indicating the CORS policy permits arbitrary domains
You are affected if Norton Password Manager version is earlier than 6.6.2.5 AND the CORS policy allows cross-origin requests from arbitrary domains (wildcard or non-whitelisted origins).
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 data6.6.2.5
Upgrade Norton Password Manager to version 6.6.2.5 or later. Additionally, review and restrict CORS policies to whitelist only trusted domains rather than allowing unrestricted cross-origin access.
- Consultation2.0 h
- Implementation1.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18381 — 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-2019-18381 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