Improper Input ValidationWeakness · CWE-20

CVE-2024-0112

HIGH · 7.5 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
NVIDIA Jetson AGX Orin™ and NVIDIA IGX Orin software contain a vulnerability where an attacker can cause an improper input validation issue by escalating certain permissions to a limited degree. A successful exploit of this vulnerability might lead to code execution, denial of service, data corruption, information disclosure, or escalation of privilege.

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 confidence

NVIDIA Jetson AGX Orin and IGX Orin edge computing platforms contain an improper input validation vulnerability that allows an attacker to escalate certain permissions to a limited degree. This could potentially lead to code execution, denial of service, data corruption, information disclosure, or further privilege escalation.

MitigationApply the vendor-supplied patch or firmware update from NVIDIA for the affected Jetson AGX Orin and IGX Orin software components.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/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. Identify the Jetson hardware model
    Run 'cat /proc/cpuinfo' or check the device tree to confirm the hardware is Jetson AGX Orin or IGX Orin. The model information is typically visible in /sys/firmware/devicetree/base/model or via 'nvbootinfo' command if available.
    Affected if The device is a Jetson AGX Orin or IGX Orin platform and the installed software/firmware has not been patched to the fixed version provided by NVIDIA.
  2. Check the JetPack/L4T version
    Run 'cat /etc/nv_tegra_release' to obtain the installed JetPack version. Alternatively, use 'dpkg -l | grep -i nvidia' to list installed NVIDIA packages.
    Affected if The installed JetPack version predates the NVIDIA security update addressing CVE-2024-0112. Compare your version against NVIDIA's official advisory for the fixed release.
  3. Check the system firmware version
    Run 'nvbootctrl -d' or check the bootloader version via the UEFI interface. On Jetson devices, the firmware version can also be retrieved via 'tegrarcm_v2 --uid' or checking /proc/uboot_summary if available.
    Affected if The bootloader or firmware version is older than the version containing the CVE-2024-0112 fix as specified in NVIDIA's security bulletin.
  4. Verify the vulnerable service or component is present
    Identify which NVIDIA software component contains the improper input validation flaw. Review NVIDIA's advisory for the specific service, daemon, or module affected. Check if that component is installed and running via 'systemctl list-units' or by locating its binary/config paths.
    Affected if The vulnerable component is installed and running, and its version matches the affected versions listed in NVIDIA's CVE-2024-0112 advisory.

The environment is affected if it runs on Jetson AGX Orin or IGX Orin hardware with software/firmware versions prior to NVIDIA's patched releases for CVE-2024-0112.

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-supplied patch or firmware update from NVIDIA for the affected Jetson AGX Orin and IGX Orin software components.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0112 — 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-2024-0112 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