dbcve.org
VboxwrapperApplication · Jenkins

CVE-2022-30968

MEDIUM · 5.4 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to after 1.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Jenkins vboxwrapper Plugin 1.3 and earlier does not escape the name and description of VBox node parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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

The vboxwrapper Plugin for Jenkins versions 1.3 and earlier contains a stored XSS vulnerability where the name and description fields of VBox node parameters are not properly escaped before rendering in the UI. An attacker with Item/Configure permission can inject malicious scripts through these fields that execute when other users view the affected parameter displays.

MitigationUpgrade to vboxwrapper Plugin version 1.4 or later which contains the patch for proper output escaping. If an upgrade is not immediately possible, disable or restrict the Item/Configure permission for untrusted users until the patch can be applied.

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
VboxwrapperApplication
Affected:<= 1.3

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify vboxwrapper plugin is installed
    Navigate to Jenkins Manage Plugins > Installed tab, or use Jenkins script console: Jenkins.instance.pluginManager.plugins.each { if (it.shortName == 'vboxwrapper') println it }
    Affected if The plugin is not found in the plugin list (not affected)
  2. Check installed vboxwrapper version
    In the Installed plugins list, locate the vboxwrapper entry and note the version number displayed in the Version column
    Affected if Version is 1.3 or earlier (the plugin is vulnerable to stored XSS)
  3. Identify VBox node configurations
    Navigate to Jenkins > Nodes > [node name] > Configure, or use script console to list nodes with vboxwrapper configuration: Jenkins.instance.nodes.each { if (it.toString().contains('vbox')) println it.displayName }
    Affected if No VBox nodes exist (the XSS cannot be triggered even with vulnerable plugin)
  4. Inspect VBox node parameter fields
    Review the Name and Description fields in any VBox node or vboxwrapper-related job parameters for unsanitized HTML or script tags (e.g., <script>, javascript:, onerror=)
    Affected if The Name or Description fields contain unescaped HTML/script content that would execute when viewed

You are affected if the vboxwrapper plugin version is 1.3 or earlier AND VBox node parameters with user-controlled Name or Description fields exist in your Jenkins environment.

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 a release after 1.3
Interim mitigation

Upgrade to vboxwrapper Plugin version 1.4 or later which contains the patch for proper output escaping. If an upgrade is not immediately possible, disable or restrict the Item/Configure permission for untrusted users until the patch can be applied.

Recommended fix Moderate confidence

vboxwrapper plugin version 1.4 or later

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the vboxwrapper plugin in the list
  5. If update available, click 'Update' to upgrade to the fixed version
  6. After update, restart Jenkins to apply changes
  7. Alternatively, download the fixed plugin (.hpi) from the Jenkins plugin repository and install via 'Advanced' > 'Upload Plugin'

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

Fix this in Vboxwrapper Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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