CVE-2023-30204

9.8 CRITICAL

📋 TL;DR

Judging Management System v1.0 contains a SQL injection vulnerability in the edit_judge.php endpoint via the judge_id parameter. This allows attackers to execute arbitrary SQL commands on the database, potentially compromising the entire system. All installations of version 1.0 are affected.

💻 Affected Systems

Products:
  • Judging Management System
Versions: v1.0
Operating Systems: Any OS running PHP and MySQL/MariaDB
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations of version 1.0 are vulnerable. No special configuration required.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data manipulation, authentication bypass, and potential remote code execution via database functions.

🟠

Likely Case

Database information disclosure, data manipulation, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing exploitation.

🌐 Internet-Facing: HIGH - The vulnerable endpoint is accessible via web interface, making it directly exploitable from the internet.
🏢 Internal Only: HIGH - Even internal systems are vulnerable to authenticated or unauthenticated attacks depending on access controls.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Simple SQL injection via GET/POST parameter. Public proof-of-concept available in GitHub repository.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Implement workarounds or migrate to alternative software.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add server-side validation to ensure judge_id parameter contains only numeric values

In edit_judge.php, add: if(!is_numeric($_GET['judge_id'])) { die('Invalid input'); }

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns

ModSecurity rule: SecRule ARGS:judge_id "@detectSQLi" "id:1001,phase:2,deny"

🧯 If You Can't Patch

  • Isolate the system behind a firewall with strict access controls
  • Implement network segmentation to limit database access from web server

🔍 How to Verify

Check if Vulnerable:

Test with payload: /php-jms/edit_judge.php?judge_id=1' OR '1'='1

Check Version:

Check version in application interface or readme files

Verify Fix Applied:

Test with same payload - should return error or no data instead of executing SQL

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in PHP logs
  • Multiple requests to edit_judge.php with SQL-like parameters

Network Indicators:

  • HTTP requests containing SQL keywords in judge_id parameter
  • Unusual database query patterns from web server IP

SIEM Query:

source="web_logs" AND uri="/php-jms/edit_judge.php" AND (param="*SELECT*" OR param="*UNION*" OR param="*OR*'*'*'*")

🔗 References

📤 Share & Export