Vcenter OrchestratorApplication · VMware
CVE-2015-6934
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 · uneditedSerialized-object interfaces in VMware vRealize Orchestrator 6.x, vCenter Orchestrator 5.x, vRealize Operations 6.x, vCenter Operations 5.x, and vCenter Application Discovery Manager (vADM) 7.x allow remote attackers to execute arbitrary commands via a crafted serialized Java object, related to the Apache Commons Collections library.
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 confidenceA deserialization vulnerability in the serialized-object interfaces of VMware vRealize Orchestrator, vCenter Orchestrator, vRealize Operations, vCenter Operations, and vCenter Application Discovery Manager allows remote attackers to execute arbitrary commands via crafted serialized Java objects. The flaw stems from unsafe deserialization in the Apache Commons Collections library, enabling unauthenticated remote code execution.
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
Vcenter OrchestratorApplication
= 5.5= 5.5.1= 5.5.2= 5.5.2.1
Vrealize OrchestratorApplication
= 6.0.1= 6.0.2= 6.0.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/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 installed VMware productsReview installed software or check running services for VMware vRealize Orchestrator, vCenter Orchestrator, vRealize Operations, vCenter Operations, or vCenter Application Discovery ManagerAffected if Any of these products are installed
-
Determine product versionUse the product's about dialog, version command, or check the installed package version through the system package manager or VMware's administrative interfaceAffected if Version matches 5.5, 5.5.1, 5.5.2, 5.5.2.1 for vCenter Orchestrator or 6.0.1, 6.0.2, 6.0.3 for vRealize Orchestrator
-
Verify serialized-object interface exposureCheck network listeners for the product's web service ports (typically 8281 or 8282 for Orchestrator) and determine if they are accessible from network segmentsAffected if The web interface accepting serialized Java objects is reachable over the network
-
Confirm Apache Commons Collections usageIf filesystem access is available, inspect the application libraries for the presence of commons-collections*.jar filesAffected if Apache Commons Collections library versions known to contain the unsafe transformation vectors are present
The environment is affected if any of the listed VMware products are running the specific versions (5.5.x for vCenter Orchestrator or 6.0.x for vRealize Orchestrator) with exposed serialized-object interfaces.
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 dataApply vendor-supplied patches for the affected VMware products, or implement network segmentation and restrict access to the serialized-object interfaces if immediate patching is not feasible.
Fix this in Vcenter Orchestrator
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6934 — 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-2015-6934 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