There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - A res_pjsip_session crash was discovered in Asterisk Open Source 13.x before 13.37.1, 16.x before 16.14.1,
    17.x before 17.8.1, and 18.x before 18.0.1. and Certified Asterisk before 16.8-cert5. Upon receiving a new
    SIP Invite, Asterisk did not return the created dialog locked or referenced. This caused a gap between the
    creation of the dialog object, and its next use by the thread that created it. Depending on some off-
    nominal circumstances and timing, it was possible for another thread to free said dialog in this gap.
    Asterisk could then crash when the dialog object, or any of its dependent objects, were dereferenced or
    accessed next by the initial-creation thread. Note, however, that this crash can only occur when using a
    connection-oriented protocol (e.g., TCP or TLS, but not UDP) for SIP transport. Also, the remote client
    must be authenticated, or Asterisk must be configured for anonymous calling. (CVE-2020-28327)

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - An issue was discovered in Sangoma Asterisk 16.x before 16.16.1, 17.x before 17.9.2, and 18.x before
    18.2.1 and Certified Asterisk before 16.8-cert6. When re-negotiating for T.38, if the initial remote
    response was delayed just enough, Asterisk would send both audio and T.38 in the SDP. If this happened,
    and the remote responded with a declined T.38 stream, then Asterisk would crash. (CVE-2021-26717)

  - A res_pjsip_session crash was discovered in Asterisk Open Source 13.x before 13.37.1, 16.x before 16.14.1,
    17.x before 17.8.1, and 18.x before 18.0.1. and Certified Asterisk before 16.8-cert5. Upon receiving a new
    SIP Invite, Asterisk did not return the created dialog locked or referenced. This caused a gap between the
    creation of the dialog object, and its next use by the thread that created it. Depending on some off-
    nominal circumstances and timing, it was possible for another thread to free said dialog in this gap.
    Asterisk could then crash when the dialog object, or any of its dependent objects, were dereferenced or
    accessed next by the initial-creation thread. Note, however, that this crash can only occur when using a
    connection-oriented protocol (e.g., TCP or TLS, but not UDP) for SIP transport. Also, the remote client
    must be authenticated, or Asterisk must be configured for anonymous calling. (CVE-2020-28327)

  - An issue was discovered in res_pjsip_diversion.c in Sangoma Asterisk before 13.38.0, 14.x through 16.x
    before 16.15.0, 17.x before 17.9.0, and 18.x before 18.1.0. A crash can occur when a SIP message is
    received with a History-Info header that contains a tel-uri, or when a SIP 181 response is received that
    contains a tel-uri in the Diversion header. (CVE-2020-35652)

  - A buffer overflow in res_pjsip_diversion.c in Sangoma Asterisk versions 13.38.1, 16.15.1, 17.9.1, and
    18.1.1 allows remote attacker to crash Asterisk by deliberately misusing SIP 181 responses.
    (CVE-2020-35776)

  - Incorrect access controls in res_srtp.c in Sangoma Asterisk 13.38.1, 16.16.0, 17.9.1, and 18.2.0 and
    Certified Asterisk 16.8-cert5 allow a remote unauthenticated attacker to prematurely terminate secure
    calls by replaying SRTP packets. (CVE-2021-26712)

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 已在 13.37.1之前的 Asterisk Open Source 13.x 、 16.x 之前的 16.14.1、 17.x 之前的 17.8.1以及 18.x 之前的 18.0.1中发现 res_pjsip_session 崩溃。和低于 16.8-cert5 的 Certified Asterisk 。收到新的 SIP Invite 后Asterisk 未返回锁定或引用的创建的对话框。这造成了对话框对象的创建和创建它的线程的下一次使用之间的间隔。根据某些非正常情况和时间安排，另一个线程可能在此间隙中释放所述对话框。
    然后当初始创建线程取消引用或访问对话框对象或其任何依赖对象时Asterisk 可能崩溃。但请注意此崩溃仅在使用面向连接的 SIP 传输协议例如 TCP 或 TLS但不是 UDP时才会发生。此外远程客户端必须经过认证或者必须为匿名调用配置 Asterisk。 (CVE-2020-28327)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且廠商未提供可用的修補程式。

  - 在 Asterisk Open Source 13.x 之前的 13.37.1、 16.x 之前的 16.14.1、 17.x 之前的 17.8.1和 18.x18.0.1] 之前的 中發現 res_pjsip_session 當機。和 16.8-cert5 之前的 Certified Asterisk。當收到新的 SIP 邀請時Asterisk 並未傳回已建立的已鎖定或已參照對話方塊。這會造成對話方塊物件的建立與建立對話方塊的執行緒下次使用之間出現間隔。視某些不正常的情況和定時而定另一個執行緒可在此間隙中釋放所述對話方塊。
    然後當初始建立執行緒接下來解除參照或存取對話方塊物件或其任何相依物件時Asterisk 可能會損毀。但是請注意只有在使用 SIP 傳輸的連線導向通訊協定 (例如 TCP 或 TLS 但不是 UDP) 時才會發生此當機情況。此外遠端用戶端必須經過驗證否則 Asterisk 必須設定為使用匿名呼叫。 (CVE-2020-28327)

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - 13.37.1より前の 13.x ]、 16.x より前の 16.14.1、 17.x より前の 17.8.1、 18.x より前の 18.0.1に res_pjsip_session のクラッシュが発見されました。および 16.8-cert5 より前の Certified Asterisk に関連するベクトルを通じて、可用性に影響を与えることが可能です。新しいSIP Inviteの受信時に、Asteriskはロックまたは参照された作成済みダイアログを返しませんでした。これにより、ダイアログオブジェクトの作成と、それを作成したスレッドによるその次の使用との間にギャップが生じました。いくつかの標準的でない状況とタイミングによっては、別のスレッドがこのギャップで前述のダイアログを解放する可能性があります。
    その後、ダイアログオブジェクトまたはその依存オブジェクトのいずれかが、初期作成スレッドによって次に逆参照またはアクセスされるときに、Asterisk がクラッシュする可能性があります。ただし、このクラッシュは SIP トランスポートに接続指向プロトコル例TCP や TLS などUDP は使用しない場合にのみ発生する可能性があることに注意してください。また、リモートクライアントを認証するか、匿名呼び出し用に Asterisk を設定する必要があります。CVE-2020-28327

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - A res_pjsip_session crash was discovered in Asterisk Open Source 13.x before 13.37.1, 16.x before 16.14.1,     17.x before 17.8.1, and 18.x before 18.0.1. and Certified Asterisk before 16.8-cert5. Upon receiving a new     SIP Invite, Asterisk did not return the created dialog locked or referenced. This caused a gap between the     creation of the dialog object, and its next use by the thread that created it. Depending on some off-     nominal circumstances and timing, it was possible for another thread to free said dialog in this gap.
    Asterisk could then crash when the dialog object, or any of its dependent objects, were dereferenced or     accessed next by the initial-creation thread. Note, however, that this crash can only occur when using a     connection-oriented protocol (e.g., TCP or TLS, but not UDP) for SIP transport. Also, the remote client     must be authenticated, or Asterisk must be configured for anonymous calling. (CVE-2020-28327)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
423669	Alpine: multiple asterisk packages: security update to 18.0.1-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	2025/4/4	2026/7/2	medium
403578	Alpine: asterisk: security update to 16.14.1-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	2023/10/31	2026/7/2	medium
403578	Alpine: asterisk: security update to 16.14.1-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	2023/10/31	2026/7/2	medium
400268	Alpine: multiple asterisk packages: security update to 18.1.1-r0 (deprecated)	Tenable Cloud Security	Alpine Linux Local Security Checks	2023/8/16	2026/7/2	high
400268	Alpine: multiple asterisk packages: security update to 18.1.1-r0 (deprecated)	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	2023/8/16	2026/7/2	high
423669	Alpine: multiple asterisk packages: security update to 18.0.1-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	2025/4/4	2026/7/2	medium
252371	Linux Distros 未修补的漏洞：CVE-2020-28327	Nessus	Misc.	2025/8/20	2026/7/21	medium
252371	Linux Distros 未修補的弱點：CVE-2020-28327	Nessus	Misc.	2025/8/20	2026/7/21	medium
252371	Linux Distros のパッチ未適用の脆弱性: CVE-2020-28327	Nessus	Misc.	2025/8/20	2026/7/21	medium
252371	Linux Distros Unpatched Vulnerability : CVE-2020-28327	Nessus	Misc.	2025/8/20	2026/7/21	medium

检测

插件搜索

medium

medium

medium

high

high

medium

medium

medium

medium

medium