Vulnerability in asterisk (UBUNTU-CVE-2026-23738)

Summary

vulnerability in asterisk (UBUNTU-CVE-2026-23738). Risk of unauthorized operations or information disclosure. Exploitable via `GET /httpstatus`.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **UBUNTU-CVE-2026-23738** has been found in asterisk. Attackers can target a specific entry point like `GET /httpstatus` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: apply the vendor's official patched release. If unsure, ask your IT team or search "asterisk UBUNTU-CVE-2026-23738" on the vendor's site.

UBUNTU-CVE-2026-23738 (asterisk) — Attack vector: adjacent-network / unauthenticated Attack surface: GET /httpstatus 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. Attackers reach the vulnerable code path via `GET /httpstatus` without authentication.

📍 Affected scope

asterisk — . Attack surface: GET /httpstatus.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 `GET /httpstatus` requests with malformed payloads or SQL meta-characters. Run `grep -r 'asterisk' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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 し、稼働しているサービス・バージョンを把握する。
3
Hunt for indicators of compromise detect
```
grep 'GET /httpstatus' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで `GET /httpstatus` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
7
Post-deployment verification verify
```
Replay attack against GET /httpstatus on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。