CVE-2024-45552
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 · uneditedInformation disclosure may occur during a video call if a device resets due to a non-conforming RTCP packet that doesn`t adhere to RFC standards.
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 confidenceA vulnerability in video call functionality allows information disclosure when a device resets due to receiving a non-conforming RTCP (Real-time Transport Control Protocol) packet that doesn't adhere to RFC standards. The malformed packet triggers an uncontrolled reset that exposes sensitive data during the reset process.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
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 affected Qualcomm componentInventory your device hardware or firmware to determine if it uses any of these Qualcomm components: Apq8064au, Fastconnect 6200, Fastconnect 6700, Fastconnect 6800, Fastconnect 6900, Wcd9380, Wcd9385, or Wcd9390. Check hardware specifications, device firmware manifests, or system information interfaces.Affected if The device incorporates any of the listed Qualcomm firmware components
-
Confirm video conferencing functionalityDetermine whether the device or associated software implements video conferencing capabilities that process RTCP (Real-time Transport Control Protocol) traffic. Check enabled services, running processes, or application configurations that handle real-time video communication.Affected if Video conferencing or real-time video communication features that generate RTCP packets are enabled on the system
-
Check for crash or reset logsReview system logs, kernel logs, crash dump directories, or device management logs for unexpected reset events or crashes. Look for timestamps corresponding to video call sessions. On embedded devices, check /var/log, dmesg output, or vendor-specific diagnostic interfaces.Affected if Unexpected device resets or crash logs are present, especially during or after video conferencing sessions
-
Monitor for anomalous recovery behaviorObserve the device boot process and early startup sequences for unusual behavior, memory dump processing, or recovery mode triggers that could indicate information exposure during reset recovery.Affected if The device exhibits unexpected recovery behavior, boot loops, or processes sensitive memory content during post-reset initialization
A system is affected if it contains any of the listed Qualcomm firmware components and has video conferencing features that process RTCP packets, with evidence of abnormal resets during video sessions indicating the vulnerability has been triggered.
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 dataApply vendor patches for video calling applications and ensure RTCP packet handling properly validates RFC compliance without triggering dangerous reset conditions that could leak information.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45552 — 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-2024-45552 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