CVE-2023-25772
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 input validation in the Intel(R) Retail Edge Mobile Android application before version 3.0.301126-RELEASE may allow an authenticated user to potentially enable denial of service 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 confidenceImproper input validation in the Intel Retail Edge Mobile Android application before version 3.0.301126-RELEASE allows an authenticated user with local access to potentially cause a denial of service condition.
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.301126< 3.4.7CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Locate the Intel Retail Edge Mobile appOpen Android Settings > Apps > Find 'Intel Retail Edge' or 'Retail Edge' in your installed applications listAffected if The application is installed on the device
-
Check the installed version numberTap on the Intel Retail Edge app entry and view the Version information displayed under 'App info' or 'Version'Affected if The displayed version number is lower than 3.0.301126 or lower than 3.4.7
-
Verify the exact version string formatConfirm the full version string matches patterns like '3.x.xxxx-RELEASE' - note that versions below 3.0.301126 are affected, and versions 3.0.x through 3.4.6 are also affectedAffected if Version is 3.0.301126-RELEASE or later, or 3.4.7 or later - otherwise the version is vulnerable
You are affected if the Intel Retail Edge Mobile Android app version installed is any version before 3.0.301126-RELEASE or before 3.4.7.
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.3011263.4.7
Upgrade the Intel Retail Edge Mobile Android application to version 3.0.301126-RELEASE or later to obtain the fix for this improper input validation vulnerability.
3.0.301126-RELEASE or later (or 3.4.7+ for older branch)
- Obtain the Intel Retail Edge Mobile Android application version 3.0.301126-RELEASE or later from the official Intel distribution channel
- Uninstall the current vulnerable version of the application
- Install the updated version 3.0.301126-RELEASE (or 3.4.7+ for the alternative branch)
- Verify the installed version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25772 — 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-25772 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