AirmediaApplication · Crestron

CVE-2022-34100

HIGH · 8.8 CVSS v3.1 Published 2022-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability was discovered in the Crestron AirMedia Windows Application, version 4.3.1.39, in which a low-privileged user can gain a SYSTEM level command prompt by pre-staging a file structure prior to the installation of a trusted service executable and change permissions on that file structure during a repair operation.

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 confidence

A vulnerability in Crestron AirMedia Windows Application v4.3.1.39 allows a low-privileged local user to escalate to SYSTEM privileges by pre-staging a file structure prior to installation of a trusted service executable, then modifying permissions on that file structure during a repair operation.

MitigationApply the vendor patch or update to Crestron AirMedia version 4.3.1.39 or later; until patched, restrict local user permissions and monitor for unauthorized repair operations on the 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
AirmediaApplication
Affected:= 4.3.1.39

CVSS 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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify AirMedia application is installed
    Check for Crestron AirMedia in the system registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the installation folder in Program Files. Use 'Get-ItemProperty' or inspect Add/Remove Programs.
    Affected if Crestron AirMedia application version 4.3.1.39 is found on the system
  2. Confirm the exact installed version
    Locate the AirMedia executable (commonly AirMedia.exe or similar in the installation directory) and check its file version property using PowerShell 'Get-Item' or by right-clicking the file to view Properties > Details.
    Affected if The file version reports exactly 4.3.1.39, matching the vulnerable release
  3. Identify the trusted service executable
    Examine the AirMedia installation directory for service-related executables (such as AMService.exe or similar) that are installed as a Windows service. Use 'Get-Service' cmdlet or check the service properties in services.msc.
    Affected if A service executable associated with AirMedia is present and runs under a privileged account (such as SYSTEM or LocalSystem)
  4. Check repair operation availability
    Attempt to locate the Windows Installer repair entry for AirMedia. In Add/Remove Programs, right-click AirMedia and select Repair, or use 'msiexec /f {product-code}' to test if a repair operation can be triggered by a low-privilege user.
    Affected if A repair operation can be initiated by a standard user without administrator elevation

A system is affected if Crestron AirMedia version 4.3.1.39 is installed and a low-privileged user can trigger a repair operation that allows file permission manipulation on service executables.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch or update to Crestron AirMedia version 4.3.1.39 or later; until patched, restrict local user permissions and monitor for unauthorized repair operations on the system.

Fix this in Airmedia Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34100 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34100 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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