CVE-2019-18376
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 · uneditedA CSRF token disclosure vulnerability allows a remote attacker, with access to an authenticated Management Center (MC) user's web browser history or a network device that intercepts/logs traffic to MC, to obtain CSRF tokens and use them to perform CSRF attacks against MC.
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 confidenceThe vulnerability allows CSRF tokens to be disclosed through browser history or intercepted network traffic, typically indicating tokens are being passed via URL parameters instead of POST bodies or headers. An attacker with access to either the victim's browser history or network traffic logs can extract these tokens and perform CSRF attacks against the Management Center.
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= 2.2= 2.3= 2.4CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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.
-
Identify installed Symantec Management Center versionAccess the Management Center admin interface and navigate to Help > About, or check the version via CLI if available (e.g., 'show version' or similar command). Compare against affected versions: 2.2, 2.3, or 2.4.Affected if The installed version is 2.2, 2.3, or 2.4.
-
Capture a test login or admin action and inspect the requestLog into the Management Center as an admin and perform an action (e.g., save a setting). Use browser developer tools (Network tab) or a proxy to inspect the outgoing request. Determine whether the CSRF token appears in the URL query string or in the POST body/headers.Affected if The CSRF token is transmitted as a URL parameter (visible in the query string) rather than in the POST body or a custom header.
-
Examine browser history for token exposureOpen the browser history panel and search for Management Center URLs. Look for URLs containing 'csrf', 'token', or similar parameter names that persist in the history after performing admin actions.Affected if CSRF token values are visible in the browser history URL entries.
-
Review server or proxy access logsCheck the Management Center access logs, any reverse proxy logs, or load balancer logs for entries containing Management Center requests. Search for logged URLs that include token parameters.Affected if Access logs contain CSRF token values in logged URL paths or query strings.
You are affected if running Symantec Management Center version 2.2, 2.3, or 2.4 AND CSRF tokens are being transmitted via URL parameters instead of POST bodies or headers.
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 dataEnsure CSRF tokens are transmitted via POST request bodies or custom headers rather than URL parameters, and verify tokens are not logged in server access logs, proxies, or other logging infrastructure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18376 — 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-18376 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