An issue was discovered in Asterisk Open Source 13 before 13.18.1, 14 before 14.7.1, and 15 before 15.1.1 and Certified Asterisk 13.13 befo…
An issue was discovered in Asterisk Open Source 13 before 13.18.1, 14 before 14.7.1, and 15 before 15.1.1 and Certified Asterisk 13.13 before 13.13-cert7. A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established. When this happens the session object never gets destroyed. Eventually Asterisk can run out of memory and crash.
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
https://cwe.mitre.org/data/definitions/772.html →Open in CWE collection →An attacker performs flooding at the HTTP level to bring down only a particular web application rather than anything listening on a TCP/IP connection. This denial of service attack requires substantially fewer packets to be sent which makes DoS harder to detect. This is an equivalent of SYN flood in HTTP. The idea is to keep the HTTP session alive indefinitely and then repeat that hundreds of times. This attack targets resource depletion weaknesses in web server software. The web server will wait to attacker's responses on the initiated HTTP sessions while the connection threads are being exhausted.
https://capec.mitre.org/data/definitions/469.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked | |
| asterisk | Tracked |