dbcve.org
WranglerApplication · Suse

CVE-2022-31249

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-07
Fix available
A fix is available. Upgrade to 0.7.4 / 0.8.5 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
A Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in wrangler of SUSE Rancher allows remote attackers to inject commands in the underlying host via crafted commands passed to Wrangler. This issue affects: SUSE Rancher wrangler version 0.7.3 and prior versions; wrangler version 0.8.4 and prior versions; wrangler version 1.0.0 and prior versions.

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

OS Command Injection vulnerability in wrangler component of SUSE Rancher allows remote attackers to inject arbitrary OS commands on the underlying host through crafted input passed to the wrangler tool. The critical CVSS 9.8 score indicates this is exploitable without authentication and can lead to complete system compromise.

MitigationUpdate wrangler to a version beyond the affected releases (0.7.3, 0.8.4, and 1.0.0). If patching is immediately unfeasible, restrict network access to wrangler interfaces and implement least-privilege execution contexts to limit blast radius.

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
WranglerApplication
Affected:< 0.7.4>= 0.8.0, < 0.8.5= 1.0.0

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. Identify wrangler installation and version
    Run 'wrangler --version' or check the package manager for wrangler (e.g., 'rpm -q wrangler' or 'dpkg -l wrangler' depending on the system). If wrangler is part of a larger Rancher deployment, check the container or pod running the wrangler component.
    Affected if The installed version is 0.7.0-0.7.3, 0.8.0-0.8.4, or exactly 1.0.0
  2. Locate wrangler binary or container
    Search for wrangler executables or containers: 'which wrangler', 'find / -name wrangler 2>/dev/null', or 'docker ps | grep wrangler' if running in containers.
    Affected if Wrangler is found and its version matches the affected ranges listed above
  3. Verify wrangler network exposure
    Check if wrangler listens on network interfaces. Examine configuration files, listening ports ('netstat -tulpn' or 'ss -tulpn'), or Kubernetes service definitions for wrangler-related services.
    Affected if Wrangler is bound to a network-accessible interface (0.0.0.0) without authentication restrictions
  4. Check Rancher deployment configuration
    If wrangler is part of a Rancher installation, review the Rancher version and components: 'kubectl get pods -A | grep wrangler' or check Rancher's UI for component versions.
    Affected if Rancher is running with a wrangler component version in the affected ranges

A defender is affected if wrangler is installed and its version is 0.7.0-0.7.3, 0.8.0-0.8.4, or exactly 1.0.0, and the component is network-accessible.

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 0.7.4 / 0.8.5 or later
Fixed in 0.7.40.8.5
Interim mitigation

Update wrangler to a version beyond the affected releases (0.7.3, 0.8.4, and 1.0.0). If patching is immediately unfeasible, restrict network access to wrangler interfaces and implement least-privilege execution contexts to limit blast radius.

Recommended fix High confidence

Upgrade to wrangler >= 0.7.4, >= 0.8.5, or > 1.0.0 depending on your current major version branch

  1. Identify the current wrangler version in use by checking the project's dependencies (e.g., go.mod, package.json, or container image tags)
  2. For wrangler versions < 0.7.4: upgrade to version 0.7.4 or later
  3. For wrangler versions >= 0.8.0 and < 0.8.5: upgrade to version 0.8.5 or later
  4. For wrangler version 1.0.0: upgrade to a version higher than 1.0.0 (e.g., 1.0.1 or later)
  5. After upgrading, rebuild and redeploy the affected services to ensure the patched wrangler version is in use
  6. Verify the upgrade was successful by checking the wrangler version in the deployed environment
Caveat Minimal risk - patch releases typically contain bug fixes and security patches without breaking API changes

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

Fix this in Wrangler Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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