dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-57608

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
An issue in Via Browser 6.1.0 allows a a remote attacker to execute arbitrary code via the mark.via.Shell component.

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 · moderate confidence

Via Browser 6.1.0 contains a vulnerability in the mark.via.Shell component that allows remote attackers to execute arbitrary code, likely due to improper input validation or insufficient access controls on this exported Android component.

MitigationUpdate Via Browser to the latest patched version. If updates are unavailable, disable or restrict access to the mark.via.Shell component through proper Android permission controls or application-level 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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installed Via Browser version
    Open Android Settings > Apps > Via Browser and view the version number under 'App info', or use a package manager to query: `adb shell pm list packages -f | grep via.browser` then check the APK version
    Affected if The installed version is 6.1.0 exactly
  2. Verify mark.via.Shell component is exported
    Use ADB to query the component's export status: `adb shell dumpsys package com.via.browser | grep -A 10 'mark.via.Shell'` or decompile the APK and inspect AndroidManifest.xml for android:exported="true" on the Shell component
    Affected if The component shows android:exported="true" or is accessible without permissions in the dumpsys output
  3. Confirm component accepts external input
    Inspect the application's code or use a dynamic analysis tool to test if the mark.via.Shell component accepts and processes intent parameters without validation, or check if any intent filters expose it to other apps
    Affected if The component accepts arbitrary intent data without sanitization or lacks permission requirements like android:permission="signature"

You are affected if Via Browser version 6.1.0 is installed and the mark.via.Shell component is exported and accessible to other applications without proper validation controls.

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

Update Via Browser to the latest patched version. If updates are unavailable, disable or restrict access to the mark.via.Shell component through proper Android permission controls or application-level validation.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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