CVE-2024-37574
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 · uneditedThe GriceMobile com.grice.call application 4.5.2 for Android enables any installed application (with no permissions) to place phone calls without user interaction by sending a crafted intent via the com.iui.mobile.presentation.MobileActivity.
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 confidenceThe GriceMobile com.grice.call Android application version 4.5.2 exposes the com.iui.mobile.presentation.MobileActivity component as an exported Activity, allowing any installed application to send crafted intents that trigger phone calls without user interaction and without requiring the CALL_PHONE permission. This bypasses Android's permission model for telephony functionality.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the GriceMobile call app is installedCheck if the package com.grice.call exists on the device using a package manager query (e.g., 'pm list packages | grep com.grice.call' or via Settings > Apps)Affected if The package com.grice.call is found on the device
-
Check the installed application versionRetrieve the version of com.grice.call using 'pm dump com.grice.call | grep version' or view the app info in Settings under App versionAffected if The installed version is 4.5.2 (the only version specified as affected)
-
Extract and inspect the AndroidManifest.xmlDecompile the APK (using tools like apktool) and open AndroidManifest.xml to locate the <activity> element with android:name="com.iui.mobile.presentation.MobileActivity"Affected if The MobileActivity component is found in the manifest
-
Determine if the activity is exportedIn the AndroidManifest.xml, check if the MobileActivity element has android:exported="true" or has no android:exported attribute (which defaults to true for target API < 31)Affected if android:exported is set to true or is absent on an activity targeting API level below 31
A user is affected if the com.grice.call app version 4.5.2 is installed and the MobileActivity component has android:exported set to true (or unset on older target SDKs), allowing any app to trigger calls without permissions.
Generated from the published advisory. Verify against your own configuration.
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 dataSet android:exported="false" on the MobileActivity component in the AndroidManifest.xml, or implement a permission check (android:permission attribute) to restrict which applications can invoke the activity. Thoroughly test that legitimate call functionality remains intact after applying the fix.
- Consultation4.0 h
- Implementation3.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37574 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37574 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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