LScube libnemesi 0.6.4-rc1 rtsp_handlers.c handle_rtsp_pkt memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.6 | $0-$5k | 0.00 |
A vulnerability was found in LScube libnemesi 0.6.4-rc1. It has been rated as critical. This issue affects the function handle_rtsp_pkt
of the file rtsp_handlers.c. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Multiple buffer overflows in LScube libnemesi 0.6.4-rc1 and earlier allow remote attackers to execute arbitrary code via (1) a reply that begins with a long version string, which triggers an overflow in handle_rtsp_pkt in rtsp_handlers.c; long headers that trigger overflows in (2) send_pause_request, (3) send_play_request, (4) send_setup_request, or (5) send_teardown_request in rtsp_send.c, as demonstrated by the Content-Base header; or a long Transport header, which triggers an overflow in (6) get_transport_str_sctp, (7) get_transport_str_tcp, or (8) get_transport_str_udp in rtsp_transport.c.
The weakness was disclosed 12/27/2007 by Luigi Auriemma (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2007-6631 since 01/03/2008. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.
The exploit is available at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Exploit-DB (30943), SecurityFocus (BID 27048†) and OSVDB (42820†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/27/2007 🔍12/27/2007 🔍
01/03/2008 🔍
01/03/2008 🔍
01/25/2008 🔍
03/16/2015 🔍
01/24/2025 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Luigi Auriemma
Status: Not defined
CVE: CVE-2007-6631 (🔍)
GCVE (CVE): GCVE-0-2007-6631
GCVE (VulDB): GCVE-100-40337
SecurityFocus: 27048 - Libnemesi Multiple Remote Buffer Overflow Vulnerabilities
OSVDB: 42820 - LScube libnemesi rtsp_handlers.c handle_rtsp_pkt Function Version String Overflow
Vupen: ADV-2008-0010
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/16/2015 01:43 PMUpdated: 01/24/2025 12:30 AM
Changes: 03/16/2015 01:43 PM (52), 09/14/2018 08:07 AM (6), 01/24/2025 12:30 AM (22)
Complete: 🔍
Cache ID: 18:DAB:40
No comments yet. Languages: en.
Please log in to comment.