dbcve.org
Bosh EditorApplication · VMware

CVE-2022-31691

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-04
Fix available
A fix is available. Upgrade to 1.40.0 / 4.16.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Spring Tools 4 for Eclipse version 4.16.0 and below as well as VSCode extensions such as Spring Boot Tools, Concourse CI Pipeline Editor, Bosh Editor and Cloudfoundry Manifest YML Support version 1.39.0 and below all use Snakeyaml library for YAML editing support. This library allows for some special syntax in the YAML that under certain circumstances allows for potentially harmful remote code execution by the attacker.

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

Spring Tools 4 for Eclipse and multiple VSCode extensions (Spring Boot Tools, Concourse CI Pipeline Editor, Bosh Editor, Cloudfoundry Manifest YML Support) include the vulnerable Snakeyaml library versions that allow specially crafted YAML syntax to trigger deserialization leading to remote code execution when users open or edit malicious YAML files.

MitigationUpgrade to Spring Tools 4 version 4.16.1 or later and VSCode extensions version 1.39.1 or later which contain patched Snakeyaml library versions; avoid opening untrusted YAML files in affected tools until patched.

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
Bosh EditorApplication
Affected:>= 1.0.0, < 1.40.0
Cloudfoundry Manifest Yml SupportApplication
Affected:>= 1.0.0, < 1.40.0
Concourse Ci Pipeline EditorApplication
Affected:>= 1.0.0, < 1.40.0
Spring Boot ToolsFramework / library
Affected:>= 1.0.0, < 1.40.0
Spring ToolsFramework / library
Affected:>= 4.0.0, < 4.16.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check VSCode extension versions
    Run 'code --list-extensions' to list installed extensions, then for each of these extensions check its version: VMware.bosh-editor, VMware.cloudfoundry-manifest-yml-support, VMware.concourse-ci-pipeline-editor, VMware.spring-boot-tools
    Affected if Any of these extensions are installed with version lower than 1.40.0 (e.g., 1.0.0 to 1.39.x)
  2. Check Spring Tools 4 for Eclipse version
    In Eclipse, go to Help > About Eclipse IDE > Installation Details > Installed Software, or check the Spring Tools 4 package version in the Eclipse Marketplace
    Affected if Spring Tools 4 version is 4.0.0 or higher but lower than 4.16.1
  3. Identify vulnerable Snakeyaml library presence
    For VSCode extensions, check the extension's lib folder or manifest for snakeyaml version; for Eclipse Spring Tools, check the bundled libraries under the installation directory for snakeyaml-1.x.jar where x is below the patched version
    Affected if Snakeyaml library version is older than the patched version bundled in 1.40.0 (extensions) or 4.16.1 (Spring Tools)
  4. Verify if malicious YAML files are being processed
    Review recent file access logs or extension activity for any recently opened or edited untrusted YAML files, particularly in projects using the affected extensions
    Affected if Users have opened or edited YAML files from untrusted sources using the vulnerable tools

A user is affected if they have any of these VSCode extensions (version < 1.40.0) or Spring Tools 4 for Eclipse (version < 4.16.1) installed and actively process YAML files, especially from untrusted sources.

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
Upgrade available Upgrade to 1.40.0 / 4.16.1 or later
Fixed in 1.40.04.16.1
Interim mitigation

Upgrade to Spring Tools 4 version 4.16.1 or later and VSCode extensions version 1.39.1 or later which contain patched Snakeyaml library versions; avoid opening untrusted YAML files in affected tools until patched.

Recommended fix High confidence

Spring Tools 4 for Eclipse: upgrade to 4.16.1 or later; VSCode extensions (Spring Boot Tools, Concourse CI Pipeline Editor, Bosh Editor, Cloudfoundry Manifest YML Support): upgrade to 1.40.0 or later

  1. For Spring Tools 4 for Eclipse: Check current version via Help > About Eclipse IDE > Installation Details
  2. For Spring Tools 4 for Eclipse: Update to version 4.16.1 or later via Eclipse Marketplace or download from spring.io/tools
  3. For VSCode extensions (Spring Boot Tools, Concourse CI Pipeline Editor, Bosh Editor, Cloudfoundry Manifest YML Support): Check current installed versions in VSCode Extensions view
  4. For VSCode extensions: Update each affected extension to version 1.40.0 or later via VSCode Extensions Marketplace
  5. Restart Eclipse/VSCode after updates to ensure new versions are loaded

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

Fix this in Bosh Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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