AirmediaApplication · Crestron

CVE-2022-40298

HIGH · 8.8 CVSS v3.1 Published 2022-09-23
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
Crestron AirMedia for Windows before 5.5.1.84 has insecure inherited permissions, which leads to a privilege escalation vulnerability found in the AirMedia Windows Application, version 4.3.1.39. A low privileged user can initiate a repair of the system and gain a SYSTEM level shell.

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

Crestron AirMedia Windows Application before version 5.5.1.84 contains insecure inherited permissions that allow a low-privileged user to trigger a system repair function. This repair mechanism executes with SYSTEM-level privileges, enabling the attacker to obtain a full SYSTEM shell and complete privilege escalation.

MitigationUpgrade AirMedia Windows Application to version 5.5.1.84 or later to remediate the insecure permission vulnerability.

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. Locate AirMedia Windows Application installation
    Check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or look in C:\Program Files\Crestron\AirMedia for the AMIS.exe or similar AirMedia binaries
    Affected if The application is installed on the system
  2. Determine installed AirMedia version
    Right-click the AirMedia executable (such as AMIS.exe or AirMedia.exe) in Program Files, select Properties, and check the File Version field, or query the registry key for the DisplayVersion value
    Affected if The installed version is exactly 4.3.1.39
  3. Identify the repair mechanism executable
    Search the AirMedia installation directory for files related to repair, update, or fix functionality, such as any executable containing 'repair', 'fix', 'update', or 'service' in the filename
    Affected if A repair executable exists in the AirMedia installation folder with weak permissions
  4. Verify low-privileged user access to repair function
    Use icacls or accesschk to examine the permissions on the identified repair executable or associated Windows service - attempt to run the repair function as a standard user account
    Affected if A standard (non-admin) user account can execute the repair mechanism

A system is affected only if the AirMedia Windows Application version is exactly 4.3.1.39 AND a low-privileged user can trigger the repair mechanism that escalates to SYSTEM privileges.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade AirMedia Windows Application to version 5.5.1.84 or later to remediate the insecure permission vulnerability.

Recommended fix High confidence

5.5.1.84 or later

  1. Identify the current version of Crestron AirMedia for Windows installed on the system
  2. Download Crestron AirMedia for Windows version 5.5.1.84 or later from the official Crestron website (www.crestron.com)
  3. Follow standard upgrade procedures to apply the update to the AirMedia software
  4. After upgrade, verify the installed version is 5.5.1.84 or later to confirm remediation

Generated from the published advisory — verify against the referenced sources before acting.

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-40298 — 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-40298 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