dbcve.org
ArvadosApplication

CVE-2022-36006

HIGH · 8.8 CVSS v3.1 Published 2022-08-15
Fix available
A fix is available. Upgrade to 2.4.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Arvados is an open source platform for managing, processing, and sharing genomic and other large scientific and biomedical data. A remote code execution (RCE) vulnerability in the Arvados Workbench allows authenticated attackers to execute arbitrary code via specially crafted JSON payloads. This exists in all versions up to 2.4.1 and is fixed in 2.4.2. This vulnerability is specific to the Ruby on Rails Workbench application (“Workbench 1”). We do not believe any other Arvados components, including the TypesScript browser-based Workbench application (“Workbench 2”) or API Server, are vulnerable to this attack. For versions of Arvados earlier than 2.4.2: remove the Ruby-based "Workbench 1" app ("apt-get remove arvados-workbench") from your installation as a workaround.

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

A remote code execution vulnerability exists in Arvados Workbench 1 (Ruby on Rails) where authenticated attackers can execute arbitrary code through specially crafted JSON payloads. The vulnerability affects all versions up to 2.4.1 and was fixed in version 2.4.2. This is specific to the Ruby-based Workbench 1 application; Workbench 2 and the API Server are not affected.

MitigationUpgrade Arvados Workbench 1 to version 2.4.2 or later. Alternatively, remove the arvados-workbench package as a workaround if upgrading is not possible.

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
ArvadosApplication
Affected:< 2.4.2

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 if arvados-workbench package is installed
    Run 'dpkg -l arvados-workbench' or 'rpm -qa | grep arvados-workbench' or check your package manager for the arvados-workbench package
    Affected if Package is not installed on the system
  2. Get the installed version of arvados-workbench
    Run 'dpkg -s arvados-workbench | grep Version' or 'rpm -qi arvados-workbench' to retrieve the package version
    Affected if Version is present and less than 2.4.2
  3. Confirm this is Workbench 1, not Workbench 2
    Check that the installed package is 'arvados-workbench' (the Ruby-based Workbench 1) and not 'arvados-workbench2' (the React-based Workbench 2)
    Affected if The arvados-workbench package is present (not arvados-workbench2)
  4. Compare against affected version range
    Compare your installed version number to the affected range: all versions up to 2.4.1 are vulnerable; version 2.4.2 and later are fixed
    Affected if Installed version is less than 2.4.2

You are affected if the arvados-workbench package (the Ruby-based Workbench 1) is installed with a version lower than 2.4.2.

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 2.4.2 or later
Fixed in 2.4.2
Interim mitigation

Upgrade Arvados Workbench 1 to version 2.4.2 or later. Alternatively, remove the arvados-workbench package as a workaround if upgrading is not possible.

Recommended fix High confidence

2.4.2

  1. Upgrade Arvados to version 2.4.2 or later to resolve the vulnerability
  2. As an alternative workaround for versions earlier than 2.4.2, remove the Ruby-based Workbench 1 application by running: apt-get remove arvados-workbench

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

Fix this in Arvados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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