Unauthenticated code execution via fixed authentication key
Published Mar 13, 2024 · Updated Apr 15, 2025
Use of a hard-coded key in Intumit SmartRobot 6.1.2-202212tw and earlier allows remote attackers to gain administrator access. The authentication mechanism accepts a code produced by encrypting a user name and timestamp with a fixed key available to attackers. No credentials or user interaction are required; the forged administrator context exposes built-in system functionality that executes arbitrary code on the server.
Summary
What happened
Use of a hard-coded key in Intumit SmartRobot 6.1.2-202212tw and earlier allows remote attackers to gain administrator access. The authentication mechanism accepts a code produced by encrypting a user name and timestamp with a fixed key available to attackers. No credentials or user interaction are required; the forged administrator context exposes built-in system functionality that executes arbitrary code on the server.
The record
- CVE
- CVE-2024-2413
- Published
- Mar 13, 2024
- Updated
- Apr 15, 2025
- Vendor
- Intumit, Inc.
- Product
- SmartRobot
- Classifications
- CWE-321, CAPEC-114, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2024CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <v6.1.2-202212tw
- Affected versionversion=earlier version <=v6.1.2-202212tw
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo