CVE-2019-12827
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 · uneditedBuffer overflow in res_pjsip_messaging in Digium Asterisk versions 13.21-cert3, 13.27.0, 15.7.2, 16.4.0 and earlier allows remote authenticated users to crash Asterisk by sending a specially crafted SIP MESSAGE message.
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 confidenceBuffer overflow in Asterisk's res_pjsip_messaging module allows remote authenticated attackers to crash the server via specially crafted SIP MESSAGE messages due to insufficient bounds checking when handling incoming message content.
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>= 13.0.0, < 13.27.0>= 15.0.0, < 15.7.2>= 16.0.0, < 16.4.0= 13.21CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Determine installed Asterisk versionRun 'asterisk -V' or 'asterisk -x "core show version"' from the command line to obtain the exact Asterisk version running in your environmentAffected if The version falls within >= 13.0.0 and < 13.27.0, OR >= 15.0.0 and < 15.7.2, OR >= 16.0.0 and < 16.4.0, OR is Digium Certified Asterisk version 13.21
-
Verify res_pjsip_messaging module is loadedRun 'asterisk -x "module show like res_pjsip_messaging"' to check if the messaging module is currently loaded in memoryAffected if The module is loaded and running
-
Confirm PJSIP endpoint messaging is configuredCheck your pjsip.conf file for endpoint definitions that allow the 'message' media type, or run 'asterisk -x "pjsip show endpoints"' to list configured endpointsAffected if Endpoints are configured that accept SIP MESSAGE requests (message transport is enabled)
-
Review SIP authentication settings for messagingExamine pjsip.conf authentication settings and determine which endpoints require authentication for messaging. Check for any endpoints where 'message_auth' is set or where untrusted users can authenticateAffected if Authenticated users or any user with valid SIP credentials can send MESSAGE requests to the affected Asterisk server
If your Asterisk version is within the affected ranges listed and the res_pjsip_messaging module is loaded with endpoints that accept authenticated SIP MESSAGE requests, your environment is vulnerable to this buffer overflow.
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 data13.27.015.7.216.4.0
Upgrade Asterisk to versions beyond 16.4.0 (or apply vendor patches for 13.x/15.x branches) and restrict SIP authentication to trusted users to reduce attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12827 — 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-2019-12827 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