CVE-2022-46279
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 in the Intel(R) Retail Edge android application before version 3.0.301126-RELEASE may allow an authenticated user to potentially enable information disclosure via local access.
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 confidenceIntel(R) Retail Edge Android application versions before 3.0.301126-RELEASE contain an improper access control vulnerability that allows authenticated users to access information they should not be able to view through local access to the device.
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.0.301126CVSS 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.
-
Identify installed Intel Retail Edge app versionOn the Android device, go to Settings > Apps > Intel Retail Edge (or Intel Retail Edge Program), then check the version number listed under App infoAffected if The version shown is any build earlier than 3.0.301126-RELEASE (such as 3.0.x versions before that build, or any 2.x version)
-
Verify the app is the Retail Edge applicationConfirm the application name matches 'Intel Retail Edge' or 'Intel Retail Edge Program' in the device's installed applications listAffected if The vulnerable application is present on the device and its version is below 3.0.301126-RELEASE
-
Check if local authentication is configuredOpen the Intel Retail Edge app and determine if a local PIN, password, or biometric authentication is required to access the applicationAffected if Local authentication is used (the vulnerability allows authenticated users to bypass access controls, so an authenticated session is the trigger condition)
-
Confirm application package detailsUse Android ADB command 'adb shell dumpsys package com.intel.retailedge' (or similar package name) to retrieve detailed version and build informationAffected if The package version code or version name is lower than 3.0.301126-RELEASE
The environment is affected if the Intel Retail Edge Android application is installed at a version below 3.0.301126-RELEASE on the device.
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.0.301126
Upgrade the Intel(R) Retail Edge Android application to version 3.0.301126-RELEASE or later to obtain the access control fix.
3.0.301126-RELEASE
- Verify the current installed version of Intel(R) Retail Edge android application
- Access the Google Play Store or organization's mobile device management (MDM) system
- Search for "Intel Retail Edge" in the app store or check for available updates through the MDM console
- Update the application to version 3.0.301126-RELEASE or later
- Verify the updated version number matches 3.0.301126-RELEASE after installation
- Test the application to confirm normal functionality after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46279 — 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-46279 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