CVE-2018-12227
What it is
An issue was discovered in Asterisk Open Source 13.x before 13.21.1, 14.x before 14.7.7, and 15.x before 15.4.1 and Certified Asterisk 13.18-cert before 13.18-cert4 and 13.21-cert before 13.21-cert2. When endpoint specific ACL rules block a SIP request, they respond with a 403 forbidden. However, if an endpoint is not identified, then a 401 unauthorized response is sent. This vulnerability just discloses which requests hit a defined endpoint. The ACL rules cannot be bypassed to gain access to the disclosed endpoints.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 3.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.4% in the next 30 days (EPSS).
- Severity: 5.3 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.4% · EPSS, next 30 days
- Weakness
- CWE-200 · Information exposure
- Record status
- Modified
Affected
- Digium Asterisk < 13.21.1
- Digium Asterisk < 14.7.7
- Digium Asterisk < 15.4.1
- Digium Certified Asterisk 13.18
- Digium Certified Asterisk 13.21
- Debian Linux 9.0
Attack profile CVSS 3.0 · 5.3
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2018-12227.md and follow it. Check whether this project is affected by CVE-2018-12227. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://downloads.asterisk.org/pub/security/AST-2018-008.html
- https://issues.asterisk.org/jira/browse/ASTERISK-27818
- http://downloads.asterisk.org/pub/security/AST-2018-008.html
- https://issues.asterisk.org/jira/browse/ASTERISK-27818
References
- http://downloads.asterisk.org/pub/security/AST-2018-008.html
- http://www.securityfocus.com/bid/104455
- https://issues.asterisk.org/jira/browse/ASTERISK-27818
- https://security.gentoo.org/glsa/201811-11
- https://www.debian.org/security/2018/dsa-4320
- http://downloads.asterisk.org/pub/security/AST-2018-008.html
- http://www.securityfocus.com/bid/104455
- https://issues.asterisk.org/jira/browse/ASTERISK-27818
- https://security.gentoo.org/glsa/201811-11
- https://www.debian.org/security/2018/dsa-4320