CVE-2021-34379
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 · uneditedTrusty contains a vulnerability in the HDCP service TA where bounds checking in command 10 is missing. The length of an I/O buffer parameter is not checked, which might lead to memory corruption.
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 confidenceIn the Trusty TEE (Trusted Execution Environment), the HDCP (High-bandwidth Digital Content Protection) service Trusted Application (TA) fails to validate the length of an I/O buffer parameter in command 10 before using it. This missing bounds check allows an attacker to supply an arbitrarily large length value, potentially causing buffer overflows and memory corruption when the unchecked length is used in memory operations.
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< 32.5.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 Jetson Linux versionRun 'cat /etc/nv_tegra_release' or check the kernel version with 'uname -r'Affected if The version number is below 32.5.1 (e.g., 32.5, 32.4, etc.)
-
Confirm Trusty TEE is enabledCheck if the device has Trusty TEE support enabled, typically by examining /proc/tee_info or checking for trusty-related services in /systemAffected if Trusty TEE is present and the device is a Jetson platform
-
Verify HDCP service availabilityInspect the list of loaded Trusted Applications in Trusty TEE or check for hdcp service presence in the TEE environmentAffected if The HDCP Trusted Application is loaded on the system
-
Check for command 10 usage contextSince command 10 is internal to the HDCP TA, determine if HDCP functionality is actively used on the device (e.g., HDMI output with content protection)Affected if HDCP-protected video output is enabled and in use
The device is affected if it runs Nvidia Jetson Linux with a version prior to 32.5.1 and has Trusty TEE with the HDCP Trusted Application enabled.
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 data32.5.1
Implement strict bounds checking on all I/O buffer length parameters in command 10 of the HDCP service TA, validating buffer lengths against allocated buffer sizes before any memory operations occur.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34379 — 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-2021-34379 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