dbcve.org
Service VirtualizationApplication · Hp

CVE-2013-6221

HIGH · 10.0 CVSS v2.0 Published 2014-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges Zero-click

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
Directory traversal vulnerability in CommunicationServlet in HP Service Virtualization 3.x before 3.50.1, when the AutoPass license server is enabled, allows remote attackers to create arbitrary files and consequently execute arbitrary code via unspecified vectors, aka ZDI-CAN-2031.

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 confidence

Directory traversal vulnerability in HP Service Virtualization's CommunicationServlet allows remote attackers to traverse filesystem paths using unspecified vectors when the AutoPass license server is enabled, enabling creation of arbitrary files and subsequent remote code execution.

MitigationUpgrade to HP Service Virtualization 3.50.1 or later to patch the vulnerability; if upgrading is not immediately feasible, consider disabling the AutoPass license server if business operations permit, and restrict network access to the service.

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
Service VirtualizationApplication
Affected:= 3.0

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 if HP Service Virtualization is installed
    Look for HP Service Virtualization installation directories or check installed software listings on the system
    Affected if HP Service Virtualization is present on the system
  2. Determine the installed version of HP Service Virtualization
    Use the product's built-in version information mechanism or check installation metadata
    Affected if The version is exactly 3.0
  3. Check if the AutoPass license server feature is enabled
    Examine the product configuration or license server settings to determine if AutoPass is active
    Affected if AutoPass license server is enabled and running
  4. Verify the CommunicationServlet is accessible
    Check if the CommunicationServlet endpoint is exposed and reachable via the application's web interface or API
    Affected if The CommunicationServlet is accessible and accepts requests
  5. Inspect filesystem access controls around the application
    Review directory permissions and access controls to determine if path traversal could lead to unauthorized file creation
    Affected if The application process has write access to directories outside its intended scope

A system is affected if HP Service Virtualization version 3.0 is installed with the AutoPass license server enabled, allowing the CommunicationServlet to be exploited via directory traversal.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to HP Service Virtualization 3.50.1 or later to patch the vulnerability; if upgrading is not immediately feasible, consider disabling the AutoPass license server if business operations permit, and restrict network access to the service.

Recommended fix High confidence

HP Service Virtualization 3.50.1

  1. 1. Back up the current HP Service Virtualization installation and configuration data.
  2. 2. Download HP Service Virtualization version 3.50.1 or later from the official HP software repository.
  3. 3. Stop the HP Service Virtualization service.
  4. 4. Install version 3.50.1 following the standard upgrade procedure.
  5. 5. Verify the AutoPass license server configuration after upgrade.
  6. 6. Restart the HP Service Virtualization service.
  7. 7. Test that the CommunicationServlet functions correctly and the path traversal vulnerability is remediated.

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

Fix this in Service Virtualization Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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