CVE-2024-31224
📋 TL;DR
This vulnerability allows remote attackers to execute arbitrary code on systems running vulnerable versions of GPT Academic by sending malicious serialized data. Any device exposing GPT Academic service to the Internet is vulnerable, particularly versions 3.64 through 3.73. The vulnerability stems from unsafe deserialization of untrusted client data.
💻 Affected Systems
- GPT Academic
📦 What is this software?
Gpt Academic by Binary Husky
⚠️ Risk & Real-World Impact
Worst Case
Complete system compromise with remote code execution, allowing attackers to install malware, steal data, or pivot to other systems.
Likely Case
Remote code execution leading to data theft, service disruption, or cryptocurrency mining malware installation.
If Mitigated
Limited impact if service is isolated in a container or sandbox, but still significant risk of data exposure.
🎯 Exploit Status
The vulnerability is in the core deserialization mechanism, making exploitation straightforward for attackers with knowledge of the codebase.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 3.74
Vendor Advisory: https://github.com/binary-husky/gpt_academic/security/advisories/GHSA-jcjc-89wr-vv7g
Restart Required: Yes
Instructions:
1. Backup your current GPT Academic installation. 2. Update to version 3.74 or later using: git pull origin master. 3. Restart the GPT Academic service. 4. Verify the update was successful.
🔧 Temporary Workarounds
No workarounds available
allThe vendor states there are no known workarounds aside from upgrading to the patched version.
🧯 If You Can't Patch
- Immediately isolate the GPT Academic service from the Internet using firewall rules or network segmentation.
- Monitor the service closely for suspicious activity and implement strict access controls.
🔍 How to Verify
Check if Vulnerable:
Check the version of GPT Academic installed. If it's between 3.64 and 3.73 inclusive, it's vulnerable.Check Version:
Check the version in the GPT Academic interface or examine the source code version metadata.Verify Fix Applied:
Verify the version is 3.74 or higher and check that the commit 8af6c0cab6d96f5c4520bec85b24802e6e823f35 is present.📡 Detection & Monitoring
Log Indicators:
- Unusual deserialization errors
- Unexpected process spawns
- Abnormal network connections from the GPT Academic process
Network Indicators:
- Suspicious payloads sent to GPT Academic endpoints
- Unexpected outbound connections from the server
SIEM Query:
process:gpt_academic AND (event_type:process_creation OR event_type:network_connection) WHERE destination_ip NOT IN [allowed_ips]🔗 References
- https://github.com/binary-husky/gpt_academic/commit/8af6c0cab6d96f5c4520bec85b24802e6e823f35
- https://github.com/binary-husky/gpt_academic/pull/1648
- https://github.com/binary-husky/gpt_academic/security/advisories/GHSA-jcjc-89wr-vv7g
- https://github.com/binary-husky/gpt_academic/commit/8af6c0cab6d96f5c4520bec85b24802e6e823f35
- https://github.com/binary-husky/gpt_academic/pull/1648
- https://github.com/binary-husky/gpt_academic/security/advisories/GHSA-jcjc-89wr-vv7g
