CVE-2014-8413
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 · uneditedThe res_pjsip_acl module in Asterisk Open Source 12.x before 12.7.1 and 13.x before 13.0.1 does not properly create and load ACLs defined in pjsip.conf at startup, which allows remote attackers to bypass intended PJSIP ACL rules.
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 confidenceThe res_pjsip_acl module in Asterisk 12.x and 13.x fails to properly initialize and load Access Control Lists configured in pjsip.conf at startup. This causes PJSIP ACL rules to be ineffective, allowing remote attackers to bypass intended IP-based restrictions on SIP connections.
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>= 12.0.0, < 12.7.1>= 13.0.0, < 13.0.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check installed Asterisk versionRun 'asterisk -V' or 'asterisk --version' to display the version numberAffected if Version is 12.0.0 through 12.7.0, or 13.0.0 (any 13.0.x before 13.0.1)
-
Verify res_pjsip_acl module is loadedRun 'module show like pjsip_acl' at the Asterisk CLI to check if the module is loadedAffected if The module shows as loaded in the output
-
Confirm PJSIP is in useCheck for PJSIP configuration files in /etc/asterisk/ (pjsip.conf, extensions.conf referencing PJSIP endpoints) or run 'pjsip show endpoints' at the CLIAffected if PJSIP endpoints or transports are configured and visible in the system
-
Inspect pjsip.conf for ACL rulesExamine /etc/asterisk/pjsip.conf for ACL configurations: look for 'acl=' statements or [acl] sections that define IP-based access controlAffected if ACL rules are defined in pjsip.conf to restrict SIP connections by IP address
-
Verify ACL enforcement is workingTest from an IP address not in the ACL list - attempt a SIP INVITE to the Asterisk server using a PJSIP endpoint and observe if the connection is accepted despite being from a non-allowed IPAffected if Connections from IPs not listed in the PJSIP ACL are accepted when they should be denied
You are affected if Asterisk version is 12.0.0-12.7.0 or 13.0.0, you are using PJSIP with ACL rules configured in pjsip.conf, and connections from non-allowed IP addresses are being accepted when they should be blocked.
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 data12.7.113.0.1
Upgrade Asterisk to version 12.7.1 or 13.0.1 or later to resolve the ACL initialization failure in the res_pjsip_acl module.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8413 — 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-2014-8413 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