CVE-2013-7100: Buffer Overflow

Published Dec 19, 2013
·
Updated

Buffer overflow in the unpacksms16 function in apps/appsms.c in Asterisk Open Source 1.8.x before 1.8.24.1, 10.x before 10.12.4, and 11.x before 11.6.1; Asterisk with Digiumphones 10.x-digiumphones before 10.12.4-digiumphones; and Certified Asterisk 1.8.x before 1.8.15-cert4 and 11.x before 11.2-cert3 allows remote attackers to cause a denial of service (daemon crash) via a 16-bit SMS message with an odd number of bytes, which triggers an infinite loop.

Affected Software

81 affected components
Digium Asterisk=1.8.17.0
Digium Asterisk=1.8.17.0-rc1
Digium Asterisk=1.8.17.0-rc2
Digium Asterisk=1.8.17.0-rc3
Digium Asterisk=1.8.18.0
Digium Asterisk=1.8.18.0-rc1
Digium Asterisk=1.8.18.1
Digium Asterisk=1.8.19.0
Digium Asterisk=1.8.19.0-rc1
Digium Asterisk=1.8.19.0-rc3
Digium Asterisk=1.8.19.1
Digium Asterisk=1.8.20.0
Digium Asterisk=1.8.20.0-rc1
Digium Asterisk=1.8.20.0-rc2
Digium Asterisk=1.8.21.0-rc1
Digium Asterisk=1.8.21.0-rc2
Digium Asterisk=1.8.22.0
Digium Asterisk=1.8.22.0-rc1
Digium Asterisk=1.8.22.0-rc2
Digium Asterisk=1.8.23.0
Digium Asterisk=1.8.23.0-rc1
Digium Asterisk=1.8.23.0-rc2
Digium Asterisk=10.10.0
Digium Asterisk=10.10.0-rc1
Digium Asterisk=10.10.0-rc2
Digium Asterisk=10.11.0
Digium Asterisk=10.11.0-rc1
Digium Asterisk=10.11.0-rc2
Digium Asterisk=10.11.0-rc3
Digium Asterisk=10.12.0
Digium Asterisk=10.12.0-rc1
Digium Asterisk=10.12.0-rc2
Digium Asterisk=10.12.1
Digium Asterisk=10.12.2
Digium Asterisk=11.0.0
Digium Asterisk=11.0.0-beta1
Digium Asterisk=11.0.0-beta2
Digium Asterisk=11.0.0-rc1
Digium Asterisk=11.0.0-rc2
Digium Asterisk=11.0.1
Digium Asterisk=11.0.2
Digium Asterisk=11.1.0
Digium Asterisk=11.1.0-rc1
Digium Asterisk=11.1.0-rc3
Digium Asterisk=11.1.1
Digium Asterisk=11.1.2
Digium Asterisk=11.2.0-rc1
Digium Asterisk=11.2.0-rc2
Digium Asterisk=11.3.0-rc1
Digium Asterisk=11.3.0-rc2
Digium Asterisk=11.4.0
Digium Asterisk=11.4.0-rc1
Digium Asterisk=11.4.0-rc2
Digium Asterisk=11.4.0-rc3
Digium Asterisk=11.5.0
Digium Asterisk=11.5.0-rc1
Digium Asterisk=11.5.0-rc2
Digium Asterisk=11.5.1
Digium Asterisk Digiumphones=10.0.0
Digium Asterisk Digiumphones=10.0.0-rc1
Digium Asterisk Digiumphones=10.0.0-rc2
Digium Asterisk Digiumphones=10.11.0
Digium Asterisk Digiumphones=10.11.0-rc1
Digium Asterisk Digiumphones=10.11.0-rc2
Digium Asterisk Digiumphones=10.11.0-rc3
Digium Asterisk Digiumphones=10.12.0
Digium Asterisk Digiumphones=10.12.0-rc1
Digium Asterisk Digiumphones=10.12.0-rc2
Digium Asterisk Digiumphones=10.12.1
Digium Asterisk Digiumphones=10.12.2
Digium Certified Asterisk=1.8.15
Digium Certified Asterisk=1.8.15-cert1
Digium Certified Asterisk=1.8.15-cert1-rc1
Digium Certified Asterisk=1.8.15-cert1-rc2
Digium Certified Asterisk=1.8.15-cert1-rc3
Digium Certified Asterisk=1.8.15-cert2
Digium Certified Asterisk=1.8.15-rc1
Digium Certified Asterisk=11.2.0
Digium Certified Asterisk=11.2.0-cert1
Digium Certified Asterisk=11.2.0-rc1
Digium Certified Asterisk=11.2.0-rc2

Event History

Dec 19, 2013
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Data Sourced
via NVD·10:55 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-7100?

CVE-2013-7100 is classified as a high severity vulnerability due to the potential for remote code execution.

2

How do I fix CVE-2013-7100?

To fix CVE-2013-7100, update Asterisk to the latest version that addresses this vulnerability.

3

Which versions of Asterisk are affected by CVE-2013-7100?

CVE-2013-7100 affects Asterisk versions 1.8.x before 1.8.24.1, 10.x before 10.12.4, and 11.x before 11.6.1.

4

What is the cause of CVE-2013-7100?

CVE-2013-7100 is caused by a buffer overflow in the unpacksms16 function in the Asterisk code.

5

Is there a workaround for CVE-2013-7100?

There are no official workarounds for CVE-2013-7100; updating to a patched version is the recommended approach.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203