dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-39283

HIGH · 7.5 CVSS v3.1 Published 2022-10-12
Fix available
A fix is available. Upgrade to 2.8.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
FreeRDP is a free remote desktop protocol library and clients. All FreeRDP based clients when using the `/video` command line switch might read uninitialized data, decode it as audio/video and display the result. FreeRDP based server implementations are not affected. This issue has been patched in version 2.8.1. If you cannot upgrade do not use the `/video` switch.

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

FreeRDP clients using the /video command-line switch can read uninitialized memory, decode it as audio/video data, and display it. This is an information disclosure vulnerability where uninitialized buffer contents are processed as legitimate media stream data, affecting only client implementations.

MitigationUpgrade FreeRDP to version 2.8.1 or later which contains the patch. If upgrading is not feasible, avoid using the /video switch in affected clients.

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
FedoraOperating system
Affected:= 35= 36= 37
FreerdpApplication
Affected:< 2.8.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Check if FreeRDP client is installed
    Run 'which xfreerdp' on Linux or check installed packages via 'rpm -qa | grep -i freerdp' (RHEL/Fedora) or 'dpkg -l | grep -i freerdp' (Debian/Ubuntu)
    Affected if No FreeRDP client found means not affected by this specific client-side vulnerability
  2. Determine installed FreeRDP version
    Run 'xfreerdp --version' or 'freerdp-version' command, or inspect the package version from the package manager (rpm -q freerdp or dpkg -l freerdp)
    Affected if Cannot determine version means further investigation needed
  3. Compare version against affected range
    Compare the installed version number to the vulnerable range: versions prior to 2.8.1 are affected (for example 2.8.0, 2.7.0, 2.6.0, etc.)
    Affected if Installed version is less than 2.8.1 means the client binary itself is vulnerable
  4. Check for /video switch usage
    Review any scripts, automation, or documentation that invoke FreeRDP with the /video command-line option; also check command history for recent usage
    Affected if The /video switch must be actively used for this vulnerability to be exploitable; without it, the client is not vulnerable to this specific flaw

A user is affected if they have FreeRDP version older than 2.8.1 AND actively use the /video switch when connecting to remote servers.

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
Upgrade available Upgrade to 2.8.1 or later
Fixed in 2.8.1
Interim mitigation

Upgrade FreeRDP to version 2.8.1 or later which contains the patch. If upgrading is not feasible, avoid using the /video switch in affected clients.

Recommended fix High confidence

FreeRDP 2.8.1

  1. Upgrade FreeRDP to version 2.8.1 or later
  2. Verify the upgrade by checking the installed version (e.g., freerdp --version)
  3. If upgrading is not possible, avoid using the /video command line switch in FreeRDP clients
Caveat Minimal - this is a bug fix for an out-of-bounds read; however, test audio/video functionality after upgrade

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

Fix this in Fedora 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 the upgrade done

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-39283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-39283 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