CVE-2024-23727
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 YI Smart Kami Vision com.kamivision.yismart application through 1.0.0_20231219 for Android allows a remote attacker to execute arbitrary JavaScript code via an implicit intent to the com.ants360.yicamera.activity.WebViewActivity 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 confidenceThe YI Smart Kami Vision Android application (com.kamivision.yismart) through version 1.0.0_20231219 exposes a WebViewActivity component (com.ants360.yicamera.activity.WebViewActivity) that accepts and executes arbitrary JavaScript code sent via implicit intents, allowing any application or attacker able to send intents to this exported component to achieve remote code execution within the WebView context.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check if YI Smart Kami Vision app is installedRun 'adb shell pm list packages | grep -i kamivision' or 'adb shell pm list packages | grep -i yicamera' to find the installed package nameAffected if Package com.kamivision.yismart or com.ants360.yicamera is present on the device
-
Get the installed application versionRun 'adb shell dumpsys package <package_name>' and look for versionName and versionCode, or use 'adb shell pm dump <package_name> | grep -E "versionName|versionCode"'Affected if versionName is 1.0.0_20231219 or earlier (no patch applied)
-
Verify the WebViewActivity component is exportedRun 'adb shell dumpsys package <package_name>' and look for 'android:exported=true' under the WebViewActivity component (com.ants360.yicamera.activity.WebViewActivity), or decompile the APK and inspect AndroidManifest.xmlAffected if The WebViewActivity component has android:exported="true" in the manifest
-
Confirm JavaScript execution is reachable via intentsAnalyze the WebViewActivity code (via decompiled APK) to verify it loads intent data directly into WebView.evaluateJavascript() without validation, or test by sending a crafted intent with JavaScript payloadAffected if The component accepts intent extras and passes them directly to WebView without sanitization or source validation
The device is affected if the YI Smart Kami Vision app is installed with version 1.0.0_20231219 or earlier AND the WebViewActivity component is exported and processes JavaScript from intent data without validation.
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 dataUpdate to a patched version of the application that implements proper intent source validation and restricts JavaScript execution to explicitly trusted sources only, or disable the exported status of the WebViewActivity if not needed for legitimate inter-app communication.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23727 — 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-23727 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