dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-31974

MEDIUM · 6.3 CVSS v3.1 Published 2024-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The com.solarized.firedown (aka Solarized FireDown Browser & Downloader) application 1.0.76 for Android allows a remote attacker to execute arbitrary JavaScript code via a crafted intent. com.solarized.firedown.IntentActivity uses a WebView component to display web content and doesn't adequately sanitize the URI or any extra data passed in the intent by any installed application (with no permissions).

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 Android app's IntentActivity component uses a WebView to display web content but fails to sanitize intent data (URI and extras) from any installed application. An attacker can send a crafted intent containing a malicious URI (e.g., javascript: payload) that gets loaded in the WebView, enabling arbitrary JavaScript execution within the app's WebView context.

MitigationImplement strict input validation and sanitization on all intent data before passing it to the WebView; avoid loading unvalidated URIs and consider restricting WebView JavaScript execution or using WebViewClient shouldOverrideUrlLoading for validation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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 the app containing the vulnerable IntentActivity
    Use a package manager tool (e.g., 'adb shell pm list packages' or a mobile device management scanner) to list installed apps. Cross-reference with any app name or vendor information associated with CVE-2024-31974 if available.
    Affected if The target app is installed on the device.
  2. Check if IntentActivity is exported
    Use 'adb shell dumpsys package <package_name>' to inspect the activity component. Look for the IntentActivity in the output and check if 'android:exported=true' is set in the AndroidManifest.xml.
    Affected if The activity has android:exported=true, allowing any app to send intents to it.
  3. Verify WebView is used in the IntentActivity
    Decompile the APK (using apktool or jadx) and examine the IntentActivity source code. Search for WebView instantiation and the loadUrl method being called with intent data (getData() or getStringExtra).
    Affected if The activity code shows WebView loading URIs from incoming intents without validation.
  4. Confirm JavaScript execution is enabled in WebView
    In the decompiled source, check the WebView settings. Look for 'setJavaScriptEnabled(true)' or absence of 'setJavaScriptEnabled(false)' before the WebView loads content.
    Affected if JavaScript is enabled in the WebView configuration.
  5. Test intent-based JavaScript injection dynamically
    Send a test intent from ADB: 'adb shell am start -a android.intent.action.VIEW -d "javascript:alert(document.domain)" <package_name>/.IntentActivity'. Monitor if the JavaScript executes or if the app handles it without validation.
    Affected if The WebView loads the javascript: URI from the intent without sanitization or rejection.

If the app with the vulnerable IntentActivity is installed, the activity is exported, and its WebView loads intent URIs with JavaScript enabled, then the environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on all intent data before passing it to the WebView; avoid loading unvalidated URIs and consider restricting WebView JavaScript execution or using WebViewClient shouldOverrideUrlLoading for validation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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