dbcve.org
Vrealize AutomationApplication · VMware

CVE-2018-6958

MEDIUM · 6.1 CVSS v3.0 Published 2018-04-13
Fix available
A fix is available. Upgrade to 7.3.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
VMware vRealize Automation (vRA) prior to 7.3.1 contains a vulnerability that may allow for a DOM-based cross-site scripting (XSS) attack. Exploitation of this issue may lead to the compromise of the vRA user's workstation.

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

VMware vRealize Automation versions prior to 7.3.1 contain a DOM-based cross-site scripting (XSS) vulnerability. In DOM-based XSS, client-side JavaScript processes user-supplied input and inserts it into the page DOM without proper sanitization, allowing an attacker to execute arbitrary JavaScript in the victim's browser context.

MitigationUpgrade VMware vRealize Automation to version 7.3.1 or later to remediate this vulnerability.

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
Vrealize AutomationApplication
Affected:< 7.3.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed vRealize Automation version
    Access the VMware vRealize Automation admin console or check the product's 'About' page. The version is typically displayed in the system information or can be retrieved via the management interface.
    Affected if The installed version is lower than 7.3.1 (e.g., 7.3.0, 7.2.x, 7.1.x, 7.0.x, etc.)
  2. Verify the vRealize Automation components
    Check all vRealize Automation components in the deployment including the vRA appliance, IaaS server, and any connected services. Ensure you capture the full version number including any build numbers if displayed.
    Affected if Any component in the deployment is running a version prior to 7.3.1
  3. Confirm the web interface is accessible
    DOM-based XSS requires the vulnerable web interface to be accessible. Verify that the vRealize Automation web interface (typically on port 443) is operational.
    Affected if The vRealize Automation web interface is exposed and the version is below 7.3.1

If vRealize Automation version is confirmed to be below 7.3.1 and the web interface is accessible, the environment is affected by this DOM-based XSS vulnerability.

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.

From vendor data
Upgrade available Upgrade to 7.3.1 or later
Fixed in 7.3.1
Interim mitigation

Upgrade VMware vRealize Automation to version 7.3.1 or later to remediate this vulnerability.

Fix this in Vrealize Automation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-6958 — 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-2018-6958 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