CVE-2015-7205
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 · uneditedInteger underflow in the RTPReceiverVideo::ParseRtpPacket function in Mozilla Firefox before 43.0 and Firefox ESR 38.x before 38.5 might allow remote attackers to obtain sensitive information, cause a denial of service, or possibly have unspecified other impact by triggering a crafted WebRTC RTP packet.
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 confidenceInteger underflow vulnerability in Mozilla Firefox's WebRTC RTP packet parser (RTPReceiverVideo::ParseRtpPacket) allows remote attackers to trigger via crafted RTP packets, potentially leaking sensitive information or causing denial of service.
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= 22= 23= 38.0= 38.0.1= 38.0.5= 38.1.0= 38.1.1= 38.2.0= 38.2.1= 38.3.0= 38.4.0<= 42.0= 42.1= 13.1= 13.2CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 installed Firefox versionOpen Firefox, click the menu button, select Help > About Firefox. The version number displays in the dialog. Alternatively, type 'about:support' in the address bar and locate the 'Version' field under 'Application Basics'.Affected if The version is 38.0, 38.0.1, 38.0.5, 38.1.0, 38.1.1, 38.2.0, 38.2.1, 38.3.0, 38.4.0, or any version 38.x through 42.0, or if the version is 42.0 or lower.
-
Verify WebRTC is enabledIn Firefox address bar, type 'about:config' and press Enter. Search for the 'media.peerconnection.enabled' preference. Confirm its value is set to 'true'.Affected if WebRTC is enabled (media.peerconnection.enabled = true), as the vulnerability exists in the RTPReceiverVideo::ParseRtpPacket function used by WebRTC.
-
Check operating system for Fedora packagesOpen a terminal and run 'cat /etc/fedora-release' or 'rpm -q fedora-release' to identify the Fedora version.Affected if The system runs Fedora 22 or Fedora 23 with an affected Firefox version installed.
-
Check operating system for OpenSUSE packagesOpen a terminal and run 'cat /etc/os-release' or 'lsb_release -a' to identify the OpenSUSE version.Affected if The system runs OpenSUSE 13.1, 13.2, or Leap 42.1 with an affected Firefox version installed.
You are affected if Firefox version is 42.0 or lower (including all 38.x versions) and WebRTC is enabled, particularly on Fedora 22/23 or OpenSUSE 13.1/13.2/Leap 42.1 systems.
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.
dbcve · scopedUpdate Mozilla Firefox to version 43.0 or later (or Firefox ESR 38.5+) to patch the integer underflow in the RTP packet parsing code.
Firefox 43.0 (stable) or Firefox ESR 38.5
- Upgrade Firefox to version 43.0 or later for the stable release
- If using Firefox ESR, upgrade to version 38.5 or later
- For Fedora 22 and 23 systems, run 'dnf update firefox' to apply the security fix
- For openSUSE 13.1 and 13.2 systems, run 'zypper update firefox' to apply the security fix
- For openSUSE Leap 42.1, run 'zypper update firefox' to apply the security fix
- After updating, restart Firefox to ensure the patched version is loaded
- Verify the installed Firefox version by navigating to 'about:firefox' or checking Help > About Firefox
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7205 — 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- www.mozilla.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- www.debian.org
- www.debian.org
- www.oracle.com
- www.oracle.com
- www.securityfocus.com
- www.securitytracker.com
- www.ubuntu.com
- www.ubuntu.com
- bugzilla.mozilla.org
- security.gentoo.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-7205 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