dbcve.org
Application IntegrationApplication · Google

CVE-2025-0982

CRITICAL · 10.0 CVSS v3.1 Published 2025-02-06
Fix available
A fix is available. Upgrade to after 2025-01-23 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
Sandbox escape in the JavaScript Task feature of Google Cloud Application Integration allows an actor to execute arbitrary unsandboxed code via crafted JavaScript code executed by the Rhino engine. Effective January 24, 2025, Application Integration will no longer support Rhino as the JavaScript execution engine. No further fix actions are needed.

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 sandbox escape vulnerability exists in the JavaScript Task feature of Google Cloud Application Integration. Attackers can execute arbitrary unsandboxed code by crafting malicious JavaScript executed through the Rhino engine, bypassing all security boundaries.

MitigationAs of January 24, 2025, Rhino support has been discontinued in Application Integration. Organizations must migrate any existing JavaScript Tasks that depend on Rhino to alternative execution engines; no additional security patches are required.

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
Application IntegrationApplication
Affected:<= 2025-01-23

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify JavaScript Tasks in your environment
    Open Google Cloud Console, navigate to Application Integration, and review all integration workflows to locate any tasks configured with the JavaScript execution feature.
    Affected if Any JavaScript Task exists in your Application Integration workflows
  2. Verify the JavaScript engine in use
    For each JavaScript Task found, examine the task configuration to determine which JavaScript engine is selected. Look for an explicit engine setting or version indicator.
    Affected if The task is configured to use Rhino as the JavaScript engine
  3. Check the task configuration timestamp
    Review the last modified date or version history of each JavaScript Task configuration. Compare against the January 24, 2025 mitigation date.
    Affected if JavaScript Tasks were last modified before January 24, 2025 and still use Rhino
  4. Audit integration workflows for legacy configurations
    Export or review all integration workflow definitions to search for any references to 'Rhino' or legacy JavaScript execution settings that may persist despite the engine disablement.
    Affected if Any workflow configuration still references or enables Rhino-based JavaScript execution

You are affected if any JavaScript Task in your Application Integration environment is still configured to use the Rhino engine, as this allows sandbox escape and arbitrary code execution.

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 2025-01-23
Interim mitigation

As of January 24, 2025, Rhino support has been discontinued in Application Integration. Organizations must migrate any existing JavaScript Tasks that depend on Rhino to alternative execution engines; no additional security patches are required.

Recommended fix High confidence

Any version released after January 24, 2025 (Rhino engine has been discontinued)

  1. 1. Verify your current Application Integration version is from after January 24, 2025 (when Rhino engine support was discontinued).
  2. 2. If still using a version from January 23, 2025 or earlier, no specific upgrade is needed as the vulnerable Rhino feature has been removed.
  3. 3. Confirm in the Google Cloud Console that JavaScript Tasks are no longer using the Rhino engine.
Caveat JavaScript Tasks using Rhino engine will no longer function; migrate to alternative JavaScript execution if applicable

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

Fix this in Application Integration Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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