Debian LinuxOperating system · Debian
CVE-2018-1000098
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 · uneditedTeluu PJSIP version 2.7.1 and earlier contains a Integer Overflow vulnerability in pjmedia SDP parsing that can result in Crash. This attack appear to be exploitable via Sending a specially crafted message. This vulnerability appears to have been fixed in 2.7.2.
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 confidenceAn integer overflow vulnerability exists in the pjmedia SDP (Session Description Protocol) parsing component of Teluu PJSIP versions 2.7.1 and earlier. The vulnerability can be triggered by receiving a specially crafted SDP message, leading to a crash (denial of service). This is a memory corruption issue in the parsing logic that occurs when handling malformed or oversized SDP attributes.
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
Debian LinuxOperating system
= 9.0<= 2.7.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 if PJSIP is installedRun 'dpkg -l | grep pjsip' or 'pkg-config --modversion pjsip' to list installed PJSIP packagesAffected if No PJSIP packages are found, the system is not affected by this CVE
-
Check the PJSIP versionRun 'pkg-config --modversion pjsip' or check the version file in the PJSIP installation directory (e.g., pjlib/include/pj/config.h may contain PJ_VERSION or similar version defines)Affected if The installed version is 2.7.1 or earlier, or the version cannot be determined and is suspected to be old
-
Verify the Debian version if applicableRun 'cat /etc/debian_version' to confirm if the system is running Debian 9.0Affected if The system is Debian 9.0 and has PJSIP installed from Debian packages
-
Confirm pjmedia SDP parsing is in useReview application configuration or logs to verify that PJSIP is being used for SIP signaling with SDP negotiation (this is default behavior for most PJSIP-based applications)Affected if PJSIP is being used for SIP calls or video conferencing, which involves SDP parsing by pjmedia
-
Check for recent crash logs related to SDPReview system logs (journalctl, /var/log/syslog) or application logs for segmentation faults or crashes occurring during SDP offer/answer processingAffected if Crashes are observed in pjmedia or SDP handling code and the version is <= 2.7.1
A system is affected if it runs PJSIP version 2.7.1 or earlier (or an unknown version on Debian 9.0) and uses PJSIP for SIP/SDP communication.
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 dataUpgrade PJSIP to version 2.7.2 or later to obtain the patch for this vulnerability. Organizations using PJSIP should verify their deployed version and apply the update promptly, as the exploit requires no authentication and can be triggered remotely via malicious SDP messages.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000098 — 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-2018-1000098 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