CVE-2022-46645
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 · uneditedUncontrolled resource consumption in the Intel(R) Smart Campus Android application before version 9.9 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 confidenceUncontrolled resource consumption vulnerability in the Intel Smart Campus Android application before version 9.9 allows an authenticated local user to consume excessive system resources, potentially causing denial of service. The attacker requires valid credentials and local device access to exploit this issue.
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< 9.9CVSS 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 Intel Smart Campus app on the Android deviceOpen Settings > Apps > Apps & features, then search for 'Intel Smart Campus' in the installed applications listAffected if The application is not found on the device, then the CVE does not apply
-
Determine the installed application versionTap on the Intel Smart Campus app entry in Settings > Apps, then view the 'App info' or 'Version' field displayed under the app nameAffected if The displayed version number is less than 9.9 (for example, 9.8, 9.7, etc.)
-
Confirm version source and update channelIf the app is installed, verify whether it was obtained from the official Google Play Store or an alternative distribution source by checking the 'App version' details in the app's Play Store listing if availableAffected if The installed version is a pre-9.9 release regardless of source, as the vulnerability exists in any version below 9.9
If Intel Smart Campus Android application is installed with a version number lower than 9.9, the environment is affected by this uncontrolled resource consumption vulnerability.
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 · scoped9.9
Upgrade the Intel Smart Campus Android application to version 9.9 or later from the official app distribution channel to obtain the vendor patch.
9.9
- Open the Google Play Store on the Android device
- Search for "Intel Smart Campus"
- If an update is available, tap "Update" to download and install version 9.9 or later
- Alternatively, enable automatic app updates in Google Play Store settings to ensure future updates are applied
- After updating, verify the installed version is 9.9 or higher by going to Settings > Apps > Smart Campus > Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46645 — 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-46645 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