https://feed.craftedsignal.io/tags/api-key/Trending threats, MITRE ATT&CK coverage, and detection metadata — refreshed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioSat, 11 Apr 2026 12:00:00 +0000https://feed.craftedsignal.io/briefs/2026-04-chamilo-api-key-bruteforce/Sat, 11 Apr 2026 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-04-chamilo-api-key-bruteforce/Chamilo LMS versions prior to 1.11.38 and 2.0.0-RC.3 generate predictable REST API keys, allowing attackers with knowledge of a username and approximate key creation time to brute-force access.Chamilo LMS, a popular learning management system, contains a vulnerability in versions prior to 1.11.38 and 2.0.0-RC.3 related to the generation of REST API keys (CVE-2026-33710). The API keys are generated using a flawed algorithm: md5(time() + (user_id * 5) - rand(10000, 10000)). Due to rand(10000, 10000) always returning 10000, the formula simplifies to md5(timestamp + user_id*5 - 10000). An attacker knowing a valid username and a rough estimate of when the API key was generated can brute-force the key due to the limited entropy. This vulnerability allows unauthorized access to the Chamilo LMS REST API. The vulnerability was reported and patched in versions 1.11.38 and 2.0.0-RC.3. This poses a significant threat to educational institutions and organizations using vulnerable versions of Chamilo LMS.

Attack Chain

1. Attacker identifies a target Chamilo LMS instance running a vulnerable version (prior to 1.11.38 or 2.0.0-RC.3).
2. Attacker obtains a valid username on the target Chamilo LMS instance through OSINT or credential stuffing.
3. Attacker estimates the API key creation time. This might be inferred from user activity or system logs.
4. Attacker crafts a script to generate potential API keys based on the predictable formula md5(timestamp + user_id*5 - 10000) using the known username and estimated timestamp.
5. The script iterates through a range of timestamps around the estimated creation time, generating corresponding MD5 hashes.
6. Attacker sends API requests with the generated API keys to the Chamilo LMS server.
7. The server validates the API key against the user.
8. Upon successful validation, the attacker gains unauthorized access to the Chamilo LMS REST API, potentially allowing them to modify course content, access user data, or perform other malicious actions.

Impact

Successful exploitation of CVE-2026-33710 can lead to unauthorized access to sensitive data within the Chamilo LMS, including user information, course materials, and grades. This could result in data breaches, academic fraud, and reputational damage for affected organizations. The vulnerability affects all organizations running vulnerable versions of Chamilo LMS; the number of victims is correlated to the number of vulnerable deployments.

Recommendation

• Upgrade Chamilo LMS installations to version 1.11.38 or 2.0.0-RC.3 or later to patch CVE-2026-33710.
• Monitor web server logs for unusual API requests originating from unexpected IP addresses, especially those containing potentially valid API keys by deploying the provided Sigma rule.
• Implement rate limiting on API endpoints to mitigate brute-force attempts.
• If upgrading is not immediately feasible, consider temporarily disabling the REST API.
• Review and audit user permissions within Chamilo LMS to minimize the impact of potential unauthorized access.

]]>highadvisorycve-2026-33710chamiloapi-keybrute-forcewebserverhttps://feed.craftedsignal.io/briefs/2026-03-ai-agent-auth/Mon, 16 Mar 2026 12:00:00 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-03-ai-agent-auth/A research report auditing popular AI agent projects found that 93% rely on unscoped API keys as the only authentication mechanism, leading to potential credential exposure, privilege escalation, and lateral movement within multi-agent systems.A recent audit of 30 popular AI agent frameworks, including OpenClaw, AutoGen, CrewAI, LangGraph, MetaGPT, and AutoGPT, reveals a widespread lack of robust authorization mechanisms. The report, published in March 2026, highlights that 93% of these frameworks rely solely on unscoped API keys for authentication. This means that any agent with access to the API key has full privileges, creating significant security risks. Furthermore, none of the frameworks provide per-agent cryptographic identity or revocation capabilities. In multi-agent systems, child agents inherit the full credentials of their parent agents, with no option for scope narrowing. This lack of granular control and isolation can lead to significant security breaches, including credential exposure and privilege escalation, as demonstrated by the 21,000 exposed OpenClaw instances leaking credentials and the 1.5 million API tokens exposed in the Moltbook breach.

Attack Chain

1. Attacker gains access to an unscoped API key, either through exposed instances like the 21,000 OpenClaw instances or breaches like the Moltbook incident affecting 1.5 million tokens.
2. The attacker leverages the unscoped API key to authenticate to the AI agent framework.
3. The attacker uses the API key to control an AI agent, potentially injecting malicious goals or code.
4. In multi-agent systems, the attacker exploits the inherited privileges of child agents to gain broader access.
5. The attacker leverages the agent’s capabilities to access sensitive data or perform unauthorized actions.
6. The attacker escalates privileges by exploiting vulnerabilities within the agent framework or underlying system.
7. The attacker uses the compromised agent to move laterally within the system or network.
8. The attacker achieves their objective, which could include data theft, system disruption, or further compromise of the environment.

Impact

The widespread use of unscoped API keys and lack of proper authorization in AI agent frameworks creates a significant security risk. Successful exploitation can lead to data breaches, system compromise, and reputational damage. The report cites real-world incidents, including 21,000 exposed OpenClaw instances leaking credentials and 1.5 million API tokens exposed in the Moltbook breach, demonstrating the potential for widespread impact. The lack of per-agent revocation means that if one agent is compromised, the API key for all agents must be rotated, causing significant disruption.

Recommendation

• Implement network monitoring to detect unusual traffic patterns originating from AI agent servers. Analyze outbound connections for connections to unusual or malicious domains (grantex.dev).
• Audit the configuration of AI agent frameworks to identify instances using unscoped API keys. Prioritize upgrading or replacing frameworks that lack proper authorization controls.
• Deploy the Sigma rule for detecting API key usage in command-line arguments or environment variables to identify potential credential exposure.
• Monitor for access to sensitive data or resources by AI agents and implement least-privilege access controls.
• Implement regular security audits and penetration testing of AI agent frameworks to identify and address vulnerabilities.

]]>highadvisoryai-agentapi-keyauthorizationcredential-theft