Qnx Software Development PlatformApplication · Blackberry

CVE-2024-48854

HIGH · 7.5 CVSS v3.1 Published 2025-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Off-by-one error in the TIFF image codec in QNX SDP versions 8.0, 7.1 and 7.0 could allow an unauthenticated attacker to cause an information disclosure in the context of the process using the image codec.

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

Off-by-one error in the TIFF image codec in QNX SDP allows an unauthenticated attacker to read memory beyond allocated buffer boundaries, resulting in information disclosure within the process context.

MitigationApply vendor patches for QNX SDP 7.0, 7.1, or 8.0 when available; alternatively, disable TIFF image processing in the affected system if not required.

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
Qnx Software Development PlatformApplication
Affected:= 7.0= 7.1= 8.0

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. Identify QNX SDP version
    Check the system for QNX SDP version information. Common locations include /etc/version, /etc/product_version, or running 'uname -a' to check the kernel version. On QNX systems, you may also check /usr/pkg/qnx* or look for QNX-specific version files in /etc/ or /opt/
    Affected if The installed QNX SDP version is 7.0, 7.1, or 8.0 exactly
  2. Locate TIFF codec component
    Search for the TIFF codec library on the system. Common paths on QNX may include /usr/lib/, /lib/, /usr/lib/codecs/, or /usr/lib/image/. Look for files named like libtiff*, tiff*, or image/tiff related libraries
    Affected if The TIFF codec library exists on the system at expected QNX SDP paths
  3. Determine if TIFF processing is enabled
    Check system configuration files or image processing settings to see if TIFF image decoding is enabled. This may include checking /etc/image.conf, application configurations, or runtime settings that enable or disable specific image codecs
    Affected if TIFF image processing is explicitly enabled or the system defaults to having all codecs available
  4. Check for active TIFF image handling services
    Look for processes or services that handle image conversion, thumbnail generation, or image viewing that may utilize the TIFF codec. Check running processes with 'procmap' or 'pidin' commands common to QNX, or review application logs that reference TIFF files
    Affected if Any application or service is actively processing or can process TIFF images using the built-in codec
  5. Verify application usage of TIFF codec
    Review any custom or third-party applications deployed on the system that may call the vulnerable TIFF codec library. Check application manifests, dependencies, or configuration for TIFF-related image handling capabilities
    Affected if Applications on the system depend on or reference the QNX TIFF image codec

The environment is affected if QNX SDP version 7.0, 7.1, or 8.0 is installed AND the TIFF image codec is present and enabled for processing.

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 vendor patches for QNX SDP 7.0, 7.1, or 8.0 when available; alternatively, disable TIFF image processing in the affected system if not required.

Fix this in Qnx Software Development Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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