CVE-2026-23740
Unknown Unknown - Not Provided
Arbitrary Command Execution via World-Writable Directory in Asterisk

Publication date: 2026-02-06

Last updated on: 2026-02-10

Assigner: GitHub, Inc.

Description
Asterisk is an open source private branch exchange and telephony toolkit. Prior to versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2, when ast_coredumper writes its gdb init and output files to a directory that is world-writable (for example /tmp), an attacker with write permission(which is all users on a linux system) to that directory can cause root to execute arbitrary commands or overwrite arbitrary files by controlling the gdb init file and output paths. This issue has been patched in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-06
Last Modified
2026-02-10
Generated
2026-05-07
AI Q&A
2026-02-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 70 associated CPEs
Vendor Product Version / Range
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 13.13.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 16.8.0
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 20.7
sangoma certified_asterisk 20.7
sangoma certified_asterisk 20.7
sangoma certified_asterisk 20.7
sangoma certified_asterisk 20.7
sangoma certified_asterisk 20.7
sangoma certified_asterisk 20.7
sangoma certified_asterisk 20.7
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 18.9
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 16.8
sangoma certified_asterisk 20.7
sangoma certified_asterisk 13.13.0
sangoma asterisk to 20.18.2 (exc)
sangoma asterisk From 21.0.0 (inc) to 21.12.1 (exc)
sangoma asterisk From 22.0.0 (inc) to 22.8.2 (exc)
sangoma asterisk From 23.0.0 (inc) to 23.2.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-427 The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-23740 is a vulnerability in the ast_coredumper component of the Asterisk software. The issue occurs because ast_coredumper runs with root privileges and writes GDB initialization files and output files to a world-writable directory, such as /tmp. Since all users on a Linux system can write to this directory, an attacker can manipulate the GDB init file or output paths to execute arbitrary commands or overwrite files as root.

The vulnerability arises from the fact that GDB initialization files can contain commands that get executed by GDB. An attacker can pre-create or modify the /tmp/.gdbinit file or race the script to change it before GDB runs, leading to privilege escalation. Additionally, the script uses a trap command to delete the gdb init file on exit, which can be exploited to delete arbitrary files.

This vulnerability has been patched in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2 of Asterisk.


How can this vulnerability impact me? :

This vulnerability allows a local attacker with write access to a world-writable directory to escalate their privileges to root by manipulating GDB initialization files executed by the ast_coredumper process running as root.

The attacker can execute arbitrary commands with root privileges or overwrite arbitrary files, potentially compromising the entire system.

Additionally, the attacker can exploit the deletion mechanism of the gdb init file to delete arbitrary files, further increasing the potential damage.

However, the vulnerability is rated with low severity and a CVSS v3.1 base score of 0.0, indicating that exploitation requires local access and user interaction, and it does not impact confidentiality, integrity, or availability directly.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking if the ast_coredumper component of Asterisk is writing GDB initialization files and output files to a world-writable directory such as /tmp.

You can verify the permissions of the directory where ast_coredumper writes its files to see if it is world-writable, which would allow exploitation.

  • Run: ls -ld /tmp
  • Check for the presence of .gdbinit files or symlinks in /tmp: ls -l /tmp/.gdbinit
  • Verify the version of Asterisk installed to determine if it is vulnerable: asterisk -V

If the directory is world-writable and the Asterisk version is prior to the patched versions (20.7-cert9, 20.18.2, 21.12.1, 22.8.2, or 23.2.2), the system is vulnerable.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include upgrading Asterisk to one of the patched versions: 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, or 23.2.2.

Additionally, restrict write permissions on the directory where ast_coredumper writes its gdb init and output files, typically /tmp, to prevent unprivileged users from modifying or creating malicious files.

  • Change permissions on /tmp or configure ast_coredumper to use a non-world-writable directory.
  • Monitor and remove any suspicious .gdbinit files or symlinks in the writable directory.

These steps help prevent attackers from exploiting the vulnerability by controlling the gdb init file and output paths.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart