CVE-2025-12345
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security vulnerability has been detected in LLM-Claw 0.1.0/0.1.1/0.1.1a/0.1.1a-p1. The affected element is the function agent_deploy_init of the file /agents/deploy/initiate.c of the component Agent Deployment. Such manipulation leads to buffer overflow. It is possible to launch the attack remotely. A patch should be applied to remediate this issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBuffer overflow vulnerability in the agent_deploy_init function within /agents/deploy/initiate.c of LLM-Claw allows remote attackers to exploit improper buffer handling during agent deployment initialization. The vulnerability affects versions 0.1.0, 0.1.1, 0.1.1a, and 0.1.1a-p1 of the Agent Deployment component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of LLM-Claw Agent Deployment componentRun the version command or inspect the package metadata for the LLM-Claw installation (for example: lmk-claw --version, or check the installed package version via your package manager)Affected if The version matches 0.1.0, 0.1.1, 0.1.1a, or 0.1.1a-p1
-
Locate the agent_deploy_init source fileSearch for /agents/deploy/initiate.c in the installed LLM-Claw codebase or source treeAffected if The file exists in the installation, indicating the vulnerable code is present
-
Confirm agent deployment functionality is enabledCheck the LLM-Claw configuration files or runtime settings for the Agent Deployment component; look for flags such as agent_deploy_enabled, deploy_init_active, or similar settings that control whether deployment initialization runsAffected if The agent deployment feature is turned on or configured to initialize on startup
-
Review deployment initialization behaviorMonitor the process logs or trace output when the agent deployment initialization function is invoked; look for signs of buffer overflow such as crashes, memory corruption errors, or abnormal termination during the agent_deploy_init phaseAffected if The system exhibits crashes or abnormal behavior specifically during agent deployment initialization or the function is accessible over the network
You are affected if the installed version is 0.1.0, 0.1.1, 0.1.1a, or 0.1.1a-p1 AND the Agent Deployment component with the vulnerable agent_deploy_init function is enabled or accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-provided patch for this buffer overflow vulnerability in the agent_deploy_init function; until the patch is available, restrict network access to deployment endpoints and validate input bounds in the affected function.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data