CVE-2022-48077
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 · uneditedGenymotion Desktop v3.3.2 was discovered to contain a DLL hijacking vulnerability that allows attackers to escalate privileges and execute arbitrary code via a crafted DLL.
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 confidenceGenymotion Desktop v3.3.2 is vulnerable to DLL hijacking, where the application loads DLL files from locations that an attacker can control. By placing a malicious crafted DLL in the search path, an attacker can achieve privilege escalation (potentially to SYSTEM level) and execute arbitrary code with the privileges of the affected application.
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.3.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Confirm Genymotion Desktop installationCheck for Genymotion Desktop installation - typical install paths on Windows: C:\Program Files\Genymobile\Genymotion\ or C:\Users\[user]\AppData\Local\Genymobile\Genymotion\. Look for genymotion.exe binary.Affected if Genymotion Desktop is installed on the system
-
Identify installed versionRight-click genymotion.exe, select Properties, then view the Details tab to see the File Version. Alternatively, run: powershell (Get-Item 'C:\Program Files\Genymobile\Genymotion\genymotion.exe').VersionInfo.FileVersionAffected if Version displayed is exactly 3.3.2
-
Check for non-admin writable directories in DLL search pathAnalyze the application's DLL loading behavior using Process Monitor (procmon.exe) from Sysinternals. Filter by Process Name = genymotion.exe and Result = NAME NOT FOUND. Look for DLL load attempts from user-writable directories like the application directory, user profile, or temp folders.Affected if The application attempts to load DLLs from directories writable by low-privileged users (especially the application install directory or user directories)
-
Verify application runs with elevated privilegesLaunch Genymotion Desktop and check its process properties in Task Manager - look at the 'User' column to see if it runs under a privileged account (SYSTEM, Administrator, or elevated user).Affected if Genymotion Desktop runs with elevated privileges (SYSTEM, Administrator, or with UAC elevation)
A user is affected if Genymotion Desktop version 3.3.2 is installed AND the application runs with elevated privileges AND an attacker can write to any directory in the application's DLL search path.
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 dataUpdate Genymotion Desktop to the latest version that includes the patched DLL handling, or identify and remove/replace the vulnerable DLL file that the application attempts to load from an attacker-controllable location.
- 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-48077 — 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-48077 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