FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2024-03-28 15:43:32 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML IDDescription
f9f5c5a2-17b5-11e8-90b8-001999f8d30basterisk and pjsip -- multiple vulnerabilities

The Asterisk project reports:

AST-2018-002 - By crafting an SDP message with an invalid media format description Asterisk crashes when using the pjsip channel driver because pjproject's sdp parsing algorithm fails to catch the invalid media format description.

AST-2018-003 - By crafting an SDP message body with an invalid fmtp attribute Asterisk crashes when using the pjsip channel driver because pjproject's fmtp retrieval function fails to check if fmtp value is empty (set empty if previously parsed as invalid).


Discovery 2018-02-21
Entry 2018-02-22
asterisk13
< 13.19.2

pjsip
< 2.7.2

pjsip-extsrtp
< 2.7.2

https://downloads.asterisk.org/pub/security/AST-2018-002.html
https://downloads.asterisk.org/pub/security/AST-2018-003.html
92ad12b8-ec09-11eb-aef1-0897988a1c07pjsip -- Race condition in SSL socket server

pjsip reports:

There are a couple of issues found in the SSL socket:

  • A race condition between callback and destroy, due to the accepted socket having no group lock.
  • SSL socket parent/listener may get destroyed during handshake.

Discovery 2021-07-23
Entry 2021-07-23
pjsip
< 2.11.1

CVE-2021-32686
https://github.com/pjsip/pjproject/security/advisories/GHSA-cv8x-p47p-99wr
0537afa3-3ce0-11e7-bf9d-001999f8d30basterisk -- Buffer Overrun in PJSIP transaction layer

The Asterisk project reports:

A remote crash can be triggered by sending a SIP packet to Asterisk with a specially crafted CSeq header and a Via header with no branch parameter. The issue is that the PJSIP RFC 2543 transaction key generation algorithm does not allocate a large enough buffer. By overrunning the buffer, the memory allocation table becomes corrupted, leading to an eventual crash.

The multi-part body parser in PJSIP contains a logical error that can make certain multi-part body parts attempt to read memory from outside the allowed boundaries. A specially-crafted packet can trigger these invalid reads and potentially induce a crash.

This issues is in PJSIP, and so the issue can be fixed without performing an upgrade of Asterisk at all. However, we are releasing a new version of Asterisk with the bundled PJProject updated to include the fix.

If you are running Asterisk with chan_sip, this issue does not affect you.


Discovery 2017-04-12
Entry 2017-05-19
asterisk13
< 13.15.1

pjsip
< 2.6_1

pjsip-extsrtp
< 2.6_1

http://downloads.asterisk.org/pub/security/AST-2017-002.html
http://downloads.asterisk.org/pub/security/AST-2017-003.html
19b052c9-c533-11e7-8da5-001999f8d30basterisk -- Buffer overflow in pjproject header parsing can cause crash in Asterisk

The Asterisk project reports:

By carefully crafting invalid values in the Cseq and the Via header port, pjprojects packet parsing code can create strings larger than the buffer allocated to hold them. This will usually cause Asterisk to crash immediately. The packets do not have to be authenticated.


Discovery 2017-10-05
Entry 2017-11-09
Modified 2017-11-15
asterisk13
< 13.18.1

pjsip
< 2.7.1

pjsip-extsrtp
< 2.7.1

https://downloads.asterisk.org/pub/security/AST-2017-009.html