dbcve.org
AsteriskApplication · Sangoma

CVE-2024-57520

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to after 22.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insecure Permissions vulnerability in asterisk v22 allows a remote attacker to execute arbitrary code via the action_createconfig function. NOTE: this is disputed by the Supplier because the impact is limited to creating empty files outside of the Asterisk product directory (aka directory traversal) and the attack can only be performed by a privileged user who has the ability to manage the configuration.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Insecure permissions vulnerability in Asterisk v22's action_createconfig function allows a privileged user with configuration management abilities to perform directory traversal and create files outside the intended Asterisk directory. The supplier disputes the arbitrary code execution impact, claiming the issue is limited to creating empty files via path traversal.

MitigationRestrict and audit privileged users with configuration management permissions. Implement strict input validation and path sanitization on the action_createconfig function to prevent directory traversal attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AsteriskApplication
Affected:>= 22.0.0, <= 22.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Asterisk version
    Run `asterisk -V` or `asterisk --version` from command line, or send AMI action 'CoreShowVersion' via `asterisk -rx 'manager show commands'`, or check package manager with `rpm -q asterisk` or `dpkg -l asterisk`
    Affected if Version is 22.0.0 through 22.5.1 inclusive (run 'asterisk -V' and compare)
  2. Verify AMI is enabled
    Inspect the Asterisk manager configuration file (typically /etc/asterisk/manager.conf) and look for an [general] section with `enabled = yes`
    Affected if AMI (Asterisk Manager Interface) is enabled and listening on the configured port (default 5038)
  3. Identify privileged manager users
    In manager.conf, examine each user section for permissions. Look for users granted 'config', 'system', or 'write' privileges. Also run `asterisk -rx 'manager show users'` to list enabled manager users
    Affected if Any manager user account has 'config' write permissions or equivalent privileges enabled
  4. Confirm network exposure of AMI
    Check /etc/asterisk/manager.conf for the 'bindaddr' setting in the [general] section, and review firewall rules or netstat output to determine if port 5038 (default) is externally accessible
    Affected if AMI port is bound to 0.0.0.0 or an externally reachable IP address rather than 127.0.0.1

You are affected if Asterisk version is 22.0.0-22.5.1 AND AMI is enabled with manager users possessing config/write permissions accessible from your network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 22.5.1
Interim mitigation

Restrict and audit privileged users with configuration management permissions. Implement strict input validation and path sanitization on the action_createconfig function to prevent directory traversal attacks.

Recommended fix Moderate confidence

Asterisk 22.6.0 or later

  1. 1. Identify current Asterisk version using 'asterisk -V' or 'core show version'
  2. 2. Backup current Asterisk configuration directory (typically /etc/asterisk)
  3. 3. Stop Asterisk service using 'systemctl stop asterisk' or 'service asterisk stop'
  4. 4. Upgrade Asterisk to version 22.6.0 or later using your distribution's package manager or compile from source
  5. 5. Verify the new version with 'asterisk -V'
  6. 6. Start Asterisk service using 'systemctl start asterisk' or 'service asterisk start'
  7. 7. Test that Asterisk is functioning correctly with 'core show uptime'
Caveat Standard Asterisk minor version upgrades typically maintain configuration compatibility, but review Asterisk 22.6.0 release notes for any behavioral changes before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Asterisk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-57520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-57520 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data