dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-53566

MEDIUM · 5.5 CVSS v3.1 Published 2024-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
An issue in the action_listcategories() function of Sangoma Asterisk v22/22.0.0/22.0.0-rc1/22.0.0-rc2/22.0.0-pre1 allows attackers to execute a path traversal.

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

A path traversal vulnerability exists in the action_listcategories() function of Sangoma Asterisk v22.x, allowing attackers to use '../' sequences to access files outside the intended directory. The function fails to properly sanitize or validate user-supplied input used in file path construction.

MitigationApply vendor patches when available; implement strict input validation to reject path traversal sequences ('../', '..\') and enforce allowed directory boundaries in the action_listcategories() function.

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
Debian LinuxOperating system
Affected:= 11.0
AsteriskApplication
Affected:= 22.0.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify installed Asterisk product
    Run 'asterisk -V' or check your Asterisk installation to confirm it is Sangoma Asterisk and not another variant.
    Affected if The product is Sangoma Asterisk
  2. Check Asterisk version
    Execute 'asterisk -V' to retrieve the version number and compare it against the affected range (22.0.0 and later 22.x versions).
    Affected if The installed version is 22.0.0 or any 22.x release
  3. Verify Debian OS version
    Run 'cat /etc/debian_version' to confirm the Debian version.
    Affected if The system is running Debian 11.0
  4. Confirm action_listcategories function exposure
    Check if the AMI (Asterisk Manager Interface) or related HTTP/API endpoint that triggers action_listcategories() is enabled and accessible. Review manager.conf or HTTP server configuration.
    Affected if The function is exposed via an accessible management interface
  5. Inspect access controls on the function
    Review user permissions in manager.conf and any IP-based access controls (acl.conf) to determine if untrusted users can invoke the action_listcategories() action.
    Affected if Untrusted or unauthenticated users can trigger the function

You are affected if you run Sangoma Asterisk version 22.0.0 or any 22.x version on Debian 11.0, and the action_listcategories() function is accessible through an exposed management interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches when available; implement strict input validation to reject path traversal sequences ('../', '..\') and enforce allowed directory boundaries in the action_listcategories() function.

Recommended fix Moderate confidence

Asterisk 22.1.0 or later (confirmed fixed in stable release)

  1. 1. Identify the exact Asterisk version currently installed using 'asterisk -V' or 'apt list --installed | grep asterisk'
  2. 2. Upgrade Asterisk to a version later than 22.0.0 that includes the fix for CVE-2024-53566
  3. 3. On Debian 11 systems, ensure all system packages are updated: 'apt update && apt upgrade'
  4. 4. After upgrading, verify the Asterisk version to confirm the fix is applied
  5. 5. Test the action_listcategories() function to ensure it no longer accepts path traversal sequences
  6. 6. Review Asterisk configuration files for any security-related settings related to HTTP AMI endpoints
Caveat Minor: Asterisk 22.x releases may have new features or configuration changes; review release notes before upgrading

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53566 — 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-53566 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