CVE-2022-41614
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 · uneditedInsufficiently protected credentials in the Intel(R) ON Event Series Android application before version 2.0 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 · moderate confidenceThe Intel(R) ON Event Series Android application before version 2.0 insufficiently protected credentials, allowing an authenticated user with local access to potentially disclose sensitive information through improper credential storage or transmission mechanisms.
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< 2.0CVSS 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.
-
Verify Intel ON Event Series app is installedOn the Android device, go to Settings > Apps > Apps, then search for 'Intel ON Event Series' or 'Intel ON' to confirm the application is present on the deviceAffected if The application is installed on the device
-
Check installed application versionIn Settings > Apps > Apps > Intel ON Event Series, view the version information displayed under the app name, or use ADB command: adb shell dumpsys package com.intel.ONE.eventseries | grep versionNameAffected if Version shown is below 2.0 (for example: 1.x.x or any version number less than 2.0)
-
Confirm app handles or stores credentialsReview the Intel ON Event Series app functionality - this application is designed to manage and transmit credentials/data for Intel hardware management, so if you use it to configure or access Intel services, it handles sensitive authentication materialAffected if The app is actively used to configure, manage, or transmit authentication credentials for Intel services or hardware
You are affected if the Intel ON Event Series Android application is installed with any version below 2.0 and the app is used to handle or store authentication credentials.
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 · scoped2.0
Upgrade to Intel ON Event Series Android application version 2.0 or later which implements proper credential protection. As a temporary mitigation, restrict physical and local access to devices running vulnerable versions.
Version 2.0 or later of Intel(R) ON Event Series Android application
- Identify the current version of the Intel(R) ON Event Series Android application installed on the device
- Open the Google Play Store or your device's app store
- Search for Intel ON Event Series
- Update the application to version 2.0 or later
- Verify the updated version by checking the app's 'About' or 'Version' information in the app settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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 $4,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41614 — 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-41614 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