Source: ofono X-Debbugs-CC: t...@security.debian.org Severity: important Tags: security
Hi, The following vulnerabilities were published for ofono. It's not clear whether they were actually reported upstream or only submitted to Red Hat Bugzilla: CVE-2023-4232[0]: | A flaw was found in ofono, an Open Source Telephony on Linux. A | stack overflow bug is triggered within the decode_status_report() | function during the SMS decoding. It is assumed that the attack | scenario is accessible from a compromised modem, a malicious base | station, or just SMS. There is a bound check for this memcpy length | in decode_submit(), but it was forgotten in decode_status_report(). https://bugzilla.redhat.com/show_bug.cgi?id=2255394 CVE-2023-4233[1]: | A flaw was found in ofono, an Open Source Telephony on Linux. A | stack overflow bug is triggered within the | sms_decode_address_field() function during the SMS PDU decoding. It | is assumed that the attack scenario is accessible from a compromised | modem, a malicious base station, or just SMS. https://bugzilla.redhat.com/show_bug.cgi?id=2255396 CVE-2023-4234[2]: | A flaw was found in ofono, an Open Source Telephony on Linux. A | stack overflow bug is triggered within the decode_submit_report() | function during the SMS decoding. It is assumed that the attack | scenario is accessible from a compromised modem, a malicious base | station, or just SMS. There is a bound check for this memcpy length | in decode_submit(), but it was forgotten in decode_submit_report(). https://bugzilla.redhat.com/show_bug.cgi?id=2255399 CVE-2023-4235[3]: | A flaw was found in ofono, an Open Source Telephony on Linux. A | stack overflow bug is triggered within the decode_deliver_report() | function during the SMS decoding. It is assumed that the attack | scenario is accessible from a compromised modem, a malicious base | station, or just SMS. There is a bound check for this memcpy length | in decode_submit(), but it was forgotten in decode_deliver_report(). https://bugzilla.redhat.com/show_bug.cgi?id=2255402 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-4232 https://www.cve.org/CVERecord?id=CVE-2023-4232 [1] https://security-tracker.debian.org/tracker/CVE-2023-4233 https://www.cve.org/CVERecord?id=CVE-2023-4233 [2] https://security-tracker.debian.org/tracker/CVE-2023-4234 https://www.cve.org/CVERecord?id=CVE-2023-4234 [3] https://security-tracker.debian.org/tracker/CVE-2023-4235 https://www.cve.org/CVERecord?id=CVE-2023-4235 Please adjust the affected versions in the BTS as needed.
