CVE-2022-39857
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 · uneditedImproper access control vulnerability in CameraTestActivity in FactoryCameraFB prior to version 3.5.51 allows attackers to access broadcasting Intent as system uid privilege.
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 confidenceImproper access control vulnerability in the CameraTestActivity component of FactoryCameraFB allows an attacker with system uid privilege to access broadcasting Intents that should be restricted. The vulnerability stems from missing or insufficient access control checks in the camera testing activity, enabling potential unauthorized access to sensitive camera functionality.
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< 3.5.51CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check if FactoryCameraFB is installedList installed packages and search for 'factorycamerafb' or 'factorycamera' using pm list packages or check application list in device settingsAffected if The package com.samsung.android.factorycamerafb or similar FactoryCameraFB package is present on the device
-
Determine the installed version of FactoryCameraFBUse 'dumpsys package <package_name>' or check app info in settings to retrieve the version code/version nameAffected if The version code/version name is lower than 3.5.51
-
Verify if CameraTestActivity component existsUse 'dumpsys package <package_name>' to list all activities and components, or use 'adb shell pm dump <package_name>' to check for CameraTestActivityAffected if The CameraTestActivity component is present in the installed package
-
Check if CameraTestActivity is exportedAnalyze the AndroidManifest.xml or use 'dumpsys package' to check the activity's exported attribute and required permissionsAffected if CameraTestActivity is exported without sufficient access control or is accessible to apps with system uid but missing proper caller verification
A device is affected if FactoryCameraFB with version below 3.5.51 is installed and the CameraTestActivity component is present and accessible without proper caller identity verification.
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.
dbcve · scoped3.5.51
Update FactoryCameraFB to version 3.5.51 or later. Alternatively, implement proper access control checks in CameraTestActivity to verify caller identity before allowing access to broadcasting Intents.
FactoryCameraFB 3.5.51
- Ensure your Samsung device is running the latest system software by checking for updates in Settings > Software Update
- Apply any available security updates that include the FactoryCameraFB version 3.5.51 patch
- Verify the FactoryCameraFB version has been updated to 3.5.51 or later through your device's app information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39857 — 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-2022-39857 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