Vulnerability in asterisk (DEBIAN-CVE-2020-28242)

Summary

Vulnerability in asterisk (DEBIAN-CVE-2020-28242). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1:16.15.0~dfsg-1 or later.

Original description

The description as published by the source.

An issue 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. If Asterisk is challenged on an outbound INVITE and the nonce is changed in each response, Asterisk will continually send INVITEs in a loop. This causes Asterisk to consume more and more memory since the transaction will never terminate (even if the call is hung up), ultimately leading to a restart or shutdown of Asterisk. Outbound authentication must be configured on the endpoint for this to occur.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as DEBIAN-CVE-2020-28242 has been found in asterisk.
Risk of unauthorized operations or information disclosure.
What to do: upgrade asterisk to 1:16.15.0~dfsg-1 or later.
If unsure, ask your IT team or search "asterisk DEBIAN-CVE-2020-28242" on the vendor's site.

DEBIAN-CVE-2020-28242 (asterisk)
Attack vector: remote (network-reachable) / no user interaction
Patched: 1:16.15.0~dfsg-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in asterisk.

📍 Affected scope

Check the vendor advisory for the affected versions of asterisk.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1:16.15.0~dfsg-1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'asterisk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'asterisk' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で asterisk を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade asterisk to 1:16.15.0~dfsg-1
```
ステージング環境で 1:16.15.0~dfsg-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:14 asterisk

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:16.15.0~dfsg-1"}]}]

References

advisory security-tracker.debian.org