dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-35222

MEDIUM · 5.9 CVSS v3.1 Published 2024-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/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
Tauri is a framework for building binaries for all major desktop platforms. Remote origin iFrames in Tauri applications can access the Tauri IPC endpoints without being explicitly allowed in the `dangerousRemoteDomainIpcAccess` in v1 and in the `capabilities` in v2. Valid commands with potentially unwanted consequences ("delete project", "transfer credits", etc.) could be invoked by an attacker that controls the content of an iframe running inside a Tauri app. This vulnerability has been patched in versions 1.6.7 and 2.0.0-beta.19.

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

Tauri applications allow remote origin iFrames to bypass IPC access controls, enabling attackers who control iframe content to invoke sensitive Tauri commands (e.g., delete project, transfer credits) without proper authorization in both v1 (dangerousRemoteDomainIpcAccess) and v2 (capabilities) configurations.

MitigationUpdate Tauri to version 1.6.7 or 2.0.0-beta.19 or later, and audit IPC access configurations to ensure only explicitly allowed origins can access endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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

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 your Tauri version
    Check the Cargo.toml file or package.json for the tauri dependency version, or run 'cargo tauri --version' if the CLI is installed
    Affected if The version is earlier than 1.6.7 (for v1) or earlier than 2.0.0-beta.19 (for v2)
  2. Check v1 dangerousRemoteDomainIpcAccess setting
    Inspect your tauri.conf.json for the 'security' section and look for 'dangerousRemoteDomainIpcAccess' - this setting controls whether remote domains can access IPC
    Affected if dangerousRemoteDomainIpcAccess is present and set to true, or if you have allowed remote domains in the 'remoteDomain' field without explicit IPC restrictions
  3. Verify v2 capabilities configuration
    Examine the src-tauri/capabilities/*.json files and check if any capability grants IPC command permissions to origins other than 'localhost' or 'app://' without explicit origin restrictions
    Affected if Capabilities grant broad IPC access to commands without restricting allowed origins, or use wildcard origins for sensitive commands
  4. Determine if your app loads remote iframes
    Review your frontend code for iframe elements with src attributes pointing to domains other than localhost or your own app origin
    Affected if Your application loads content from remote origins in iframes and uses vulnerable Tauri versions with permissive IPC settings

You are affected if you run Tauri versions before 1.6.7/2.0.0-beta.19 AND have remote origins accessible via iframes with IPC command access enabled for those origins.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Tauri to version 1.6.7 or 2.0.0-beta.19 or later, and audit IPC access configurations to ensure only explicitly allowed origins can access endpoints.

Recommended fix High confidence

Tauri v1 -> 1.6.7 or Tauri v2 -> 2.0.0-beta.19

  1. 1. Identify the current Tauri version in use by checking the Cargo.toml or package.json dependencies
  2. 2. For Tauri v1 applications: Upgrade to version 1.6.7 or later by updating the tauri dependency in Cargo.toml to version ^1.6.7 and running cargo update
  3. 3. For Tauri v2 applications: Upgrade to version 2.0.0-beta.19 or later by updating the tauri dependency to the latest 2.x beta release
  4. 4. After upgrading, rebuild the application using `cargo tauri build`
  5. 5. Verify that IPC access controls are properly configured by reviewing dangerousRemoteDomainIpcAccess (v1) or capabilities (v2) to ensure only intended domains are allowed
Caveat Beta versions (2.0.0-beta.19) may have other breaking changes from the v2 API; review Tauri v2 migration guides before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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