UBUNTU-CVE-2023-27600 (CVE-2023-27600)
Vulnerability from osv_ubuntu – Published: 2023-03-15 22:15 – Updated: 2025-10-24 05:01 – Source websiteOpenSIPS is a Session Initiation Protocol (SIP) server implementation. Prior to versions 3.1.7 and 3.2.4, OpenSIPS crashes when a malformed SDP body is received and is processed by the delete_sdp_line function in the sipmsgops module. This issue can be reproduced by calling the function with an SDP body that does not terminate by a line feed (i.e. \n). The vulnerability was found while performing black-box fuzzing against an OpenSIPS server running a configuration that made use of the functions codec_delete_except_re and codec_delete_re. The same issue was also discovered while performing coverage guided fuzzing on the function codec_delete_except_re. The crash happens because the function delete_sdp_line expects that an SDP line is terminated by a line feed (\n). By abusing this vulnerability, an attacker is able to crash the server. It affects configurations containing functions that rely on the affected code, such as the function codec_delete_except_re. Due to the sanity check that is performed in the del_lump function, exploitation of this issue will generate an abort in the lumps processing function, resulting in a Denial of Service. This issue is patched in versions 3.1.7 and 3.2.4.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "opensips",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-b2bua-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-berkeley-bin",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-berkeley-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-carrierroute-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-compression-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-console",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-cpl-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-dbhttp-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-dialplan-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-emergency-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-geoip-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-http-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-identity-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-jabber-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-json-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-ldap-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-lua-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-memcached-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-mysql-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-perl-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-postgres-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-presence-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-rabbitmq-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-radius-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-redis-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-regex-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-restclient-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-sctp-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-snmpstats-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-sqlite-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-tls-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-tlsmgm-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-unixodbc-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-wss-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-xmlrpc-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-xmpp-module",
"binary_version": "2.2.2-3build4"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "opensips",
"purl": "pkg:deb/ubuntu/opensips@2.2.2-3build4?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.2.2-3build2",
"2.2.2-3build3",
"2.2.2-3build4"
]
}
],
"aliases": [],
"details": "OpenSIPS is a Session Initiation Protocol (SIP) server implementation. Prior to versions 3.1.7 and 3.2.4, OpenSIPS crashes when a malformed SDP body is received and is processed by the `delete_sdp_line` function in the sipmsgops module. This issue can be reproduced by calling the function with an SDP body that does not terminate by a line feed (i.e. `\\n`). The vulnerability was found while performing black-box fuzzing against an OpenSIPS server running a configuration that made use of the functions `codec_delete_except_re` and `codec_delete_re`. The same issue was also discovered while performing coverage guided fuzzing on the function `codec_delete_except_re`. The crash happens because the function `delete_sdp_line` expects that an SDP line is terminated by a line feed (`\\n`). By abusing this vulnerability, an attacker is able to crash the server. It affects configurations containing functions that rely on the affected code, such as the function `codec_delete_except_re`. Due to the sanity check that is performed in the `del_lump` function, exploitation of this issue will generate an `abort` in the lumps processing function, resulting in a Denial of Service. This issue is patched in versions 3.1.7 and 3.2.4.",
"id": "UBUNTU-CVE-2023-27600",
"modified": "2025-10-24T05:01:52Z",
"published": "2023-03-15T22:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2023-27600"
},
{
"type": "REPORT",
"url": "https://github.com/OpenSIPS/opensips/security/advisories/GHSA-67w7-g4j8-3wcx"
},
{
"type": "REPORT",
"url": "https://github.com/OpenSIPS/opensips/commit/c6ab3bb406c447e30c7d33a1a8970048b4612100"
},
{
"type": "REPORT",
"url": "https://opensips.org/docs/modules/3.3.x/sipmsgops.html"
},
{
"type": "REPORT",
"url": "https://opensips.org/pub/audit-2022/opensips-audit-technical-report-full.pdf"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-27600"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2023-27600"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.