Goal Reached Thanks to every supporter โ€” we hit 100%!

Goal: 1000 CNY ยท Raised: 1325 CNY

100%

CVE-2024-48920 โ€” AI Deep Analysis Summary

CVSS 9.1 ยท Critical

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: Access Control Error in Putong Online Judge. <br>๐Ÿ’ฅ **Consequences**: Non-privileged users can escalate privileges to admin level. This compromises sensitive data and system integrity.โ€ฆ

Q2Root Cause? (CWE/Flaw)

๐Ÿ›ก๏ธ **CWE**: CWE-306 (Improper Control of a Single Resource for Multiple Functions). <br>๐Ÿ” **Flaw**: The system fails to properly enforce access controls.โ€ฆ

Q3Who is affected? (Versions/Components)

๐Ÿ“ฆ **Product**: Putong Online Judge (PutongOJ). <br>๐Ÿ‘ค **Vendor**: acm309. <br>๐Ÿ“‰ **Affected Versions**: All versions **before** 2.1.0-beta.1. If you are running an older beta or stable release, you are vulnerable.

Q4What can hackers do? (Privileges/Data)

๐Ÿ•ต๏ธ **Hacker Actions**: Execute **Administrator-level operations**. <br>๐Ÿ“‚ **Data Impact**: Access to sensitive data. <br>โš ๏ธ **System Impact**: Compromise of system integrity.โ€ฆ

Q5Is exploitation threshold high? (Auth/Config)

โšก **Threshold**: **LOW**. <br>๐Ÿ”‘ **Auth**: No authentication required (PR:N). <br>๐ŸŒ **Network**: Network accessible (AV:N). <br>๐ŸŽฏ **Complexity**: Low (AC:L). No user interaction needed (UI:N). Easy to exploit remotely.

Q6Is there a public Exp? (PoC/Wild Exploitation)

๐Ÿงจ **Public Exploit**: **No**. The `pocs` field is empty in the provided data. While the flaw is clear, no specific Proof-of-Concept (PoC) code is publicly available in this dataset yet.

Q7How to self-check? (Features/Scanning)

๐Ÿ” **Self-Check**: Check your PutongOJ version. <br>๐Ÿ“‹ **Scan**: Look for version strings < 2.1.0-beta.1. <br>๐Ÿ›ก๏ธ **Monitor**: Watch for unusual admin-level actions performed by standard user accounts in logs.

Q8Is it fixed officially? (Patch/Mitigation)

โœ… **Fixed**: **YES**. <br>๐Ÿ“ฆ **Patch**: Version **2.1.0-beta.1** fixes this issue. <br>๐Ÿ”— **Source**: See GitHub release tag v2.1.0-beta.1 and the security advisory GHSA-gj6h-73c5-xw6f.

Q9What if no patch? (Workaround)

๐Ÿšง **Workaround**: If you cannot upgrade immediately: <br>1. Restrict network access to the OJ instance. <br>2. Implement strict WAF rules to block suspicious request patterns targeting admin endpoints. <br>3.โ€ฆ

Q10Is it urgent? (Priority Suggestion)

๐Ÿ”ฅ **Urgency**: **HIGH**. <br>๐Ÿ“Š **CVSS**: High severity (C:H, I:H). <br>โณ **Action**: Upgrade to v2.1.0-beta.1 immediately.โ€ฆ