Intumit SmartRobot - Use of Hard-coded Cryptographic Key
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-321.
Summary
Intumit SmartRobot uses a fixed encryption key for authentication. Remote attackers can use this key to encrypt a string composed of the user's name and timestamp to generate an authentication code. With this authentication code, they can obtain administrator privileges and subsequently execute arbitrary code on the remote server using built-in system functionality.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2024-2413
- 2026-10-03 Alias added: GHSA-gpg3-v7vj-4v8w
References
More INTUMIT Smartrobot vulnerabilities
- TI-2024-11737 Intumit SmartRobot′s Conversational AI Platform - Improper Control of Generation of Code ('Code Injection') CVSS 4.0CRITICAL 9.3
- TI-2024-00510 Intumit inc. SmartRobot - Remote Code Execution CVSS 3.1CRITICAL 9.8
- TI-2025-03141 INTUMIT SmartRobot - Server-Side Request Forgery CVSS 3.1HIGH 7.5
- TI-2024-08142 INTUMIT SmartRobot - Cross-site Scripting CVSS 3.1MEDIUM 6.1
Sources
- CVE-2024-2413 · CVE Program
- CVE-2024-2413 · NVD
- FIRST EPSS
- GHSA-gpg3-v7vj-4v8w · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences