Certified Asterisk
Approved changes feed: RSS · Atom
cpe:2.3:a:asterisk:certified_asterisk:16.8:cert14:*:*:*:*:*:*
part: a version: 16.8 update: cert14
| 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 gcve-enriched-dumps CVE data |
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.192558 |
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 |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.