CVE-2022-47361
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 · uneditedIn firewall service, there is a missing permission check. This could lead to local escalation of privilege with system execution privileges needed.
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 confidenceThis is a local privilege escalation vulnerability in a firewall service caused by a missing permission check. An attacker with existing system-level execution privileges can exploit the lack of authorization validation to elevate their privileges further, potentially gaining full control of the affected system.
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= 10.0= 11.0= 12.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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Identify Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The version is 10.0, 11.0, or 12.0 (exact versions as listed)
-
Locate the firewall service processRun 'ps -A | grep -i firewall' or check running services via 'dumpsys' in ADB shell to identify any active firewall daemonAffected if A firewall service is running on the device
-
Verify firewall service permissionsCheck the firewall service binary or APK permissions using 'ls -la /path/to/firewall' or examine its manifest via 'pm dump <package>' if it's an appAffected if The service lacks proper permission checks for privileged operations (requires code review or vendor documentation)
-
Confirm your current privilege levelRun 'id' or 'whoami' in ADB shell to determine if you have system-level execution privilegesAffected if You have system-level or root access (the attacker already needs this to exploit the missing permission check)
-
Check for firewall rule modification capabilityAttempt to view current firewall rules via 'iptables -L' or 'ip6tables -L' in ADB shell, or check if the firewall service exposes any configuration interfacesAffected if The firewall allows unprivileged or improperly authorized modification of rules
You are affected if your Android device runs version 10.0, 11.0, or 12.0 AND has a firewall service running that lacks proper authorization checks for privileged operations, AND an attacker already has system-level execution access.
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.
From vendor dataImplement proper permission and authorization checks in the firewall service to verify that the requesting user has the appropriate privileges before allowing sensitive operations. Apply any vendor-supplied patches for the affected firewall service.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47361 — 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-47361 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