Asterisk Certified Asterisk 16.8.0
Approved changes feed: RSS · Atom
cpe:2.3:a:asterisk:certified_asterisk:16.8.0:-:*:*:*:*:*:*
part: a version: 16.8.0 update: -
| Vendor | Asterisk (8cf0208b-fb97-57c9-94a0-6da40e548dcd) |
|---|---|
| Product | Certified Asterisk (57dadbdf-496a-598b-b5de-a5360c9eb937) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-42365 |
vulnerable | 2026-06-03 14:56:36.196027 |
Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan
HIGH (7.4)
Asterisk is an open source private branch exchange (PBX) and telephony toolkit. Prior to asterisk versions 18.24.2, 20.9.2, and 21.4.2 and certified-asterisk versions 18.9-cert11 and 20.7-cert2, an AMI user with `write=originate` may change all configuration files in the `/etc/asterisk/` directory. This occurs because they are able to curl remote files and write them to disk, but are also able to append to existing files using the `FILE` function inside the `SET` application. This issue may result in privilege escalation, remote code execution and/or blind server-side request forgery with arbitrary protocol. Asterisk versions 18.24.2, 20.9.2, and 21.4.2 and certified-asterisk versions 18.9-cert11 and 20.7-cert2 contain a fix for this issue.
Published: 2024-08-08T16:29:07.436Z
Updated: 2025-11-03T22:04:48.935Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-46837 |
vulnerable | 2026-06-03 14:45:46.058208 |
Details available
res_pjsip_t38 in Sangoma Asterisk 16.x before 16.16.2, 17.x before 17.9.3, and 18.x before 18.2.2, and Certified Asterisk before 16.8-cert7, allows an attacker to trigger a crash by sending an m=image line and zero port in a response to a T.38 re-invite initiated by Asterisk. This is a re-occurrence of the CVE-2019-15297 symptoms but not for exactly the same reason. The crash occurs because there is an append operation relative to the active topology, but this should instead be a replace operation.
Published: 2022-08-30T00:00:00.000Z
Updated: 2024-08-04T05:17:42.455Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.