CVE-2023-49000
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 · uneditedAn issue in ArtistScope ArtisBrowser v.34.1.5 and before allows an attacker to bypass intended access restrictions via interaction with the com.artis.browser.IntentReceiverActivity component. NOTE: this is disputed by the vendor, who indicates that ArtisBrowser 34 does not support CSS3.
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 ArtistScope ArtisBrowser Android application (versions 34.1.5 and prior) contains an access control bypass vulnerability in the com.artis.browser.IntentReceiverActivity component. This Android activity component fails to properly enforce intended access restrictions, potentially allowing unauthorized external applications or actors to trigger privileged functionality without proper authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 34.1.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Verify if ArtisBrowser app is installedRun 'adb shell pm list packages | grep -i artist' or 'adb shell pm list packages | grep -i artis' to list installed packages. The expected package name is com.artis.browser.Affected if No package matching 'artis' or 'artist' is found - the app is not installed on this device.
-
Confirm the installed version numberAfter identifying the package, run 'adb shell dumpsys package com.artis.browser' and look for the versionName or versionCode field in the output.Affected if The versionName is 34.1.5 or lower, meaning the installed version is within the affected range.
-
Check if IntentReceiverActivity is exportedRun 'adb shell dumpsys package com.artis.browser' and locate the IntentReceiverActivity entry under 'android.content.IntentReceiverActivity' in the 'Package:' section. Look for the 'exported=' attribute in the component declaration.Affected if The IntentReceiverActivity component shows 'exported=true' or no explicit 'exported=false' setting, indicating it can be invoked by external applications.
A user is affected if the ArtisBrowser app (version 34.1.5 or lower) is installed AND the IntentReceiverActivity component is exported (accessible to external apps).
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 dataRestrict the export status of IntentReceiverActivity (set android:exported='false' if not needed by external apps) and implement proper authentication/authorization checks within the activity before granting access to sensitive operations.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49000 — 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-2023-49000 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