CVE-2023-47105
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 · uneditedexec.CommandContext in Chaosblade 0.3 through 1.7.3, when server mode is used, allows OS command execution via the cmd parameter without authentication.
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 · high confidenceChaosblade 0.3 through 1.7.3 contains an unauthenticated command injection vulnerability when running in server mode. The server accepts a 'cmd' parameter which is passed directly to Go's exec.CommandContext without any authentication, allowing remote attackers to execute arbitrary operating system commands on the host.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
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 if Chaosblade is installedRun 'blade version' or check for the chaosblade binary in common locations such as /usr/local/bin/, /opt/, or the directory where it was originally installed.Affected if Chaosblade binary is found on the system
-
Determine the installed Chaosblade versionRun 'blade version' and note the version number displayed in the output.Affected if The version is 0.3 through 1.7.3 (inclusive)
-
Check if Chaosblade server mode is runningLook for a running process listening on the default Chaosblade server port (typically port 3658) using commands like 'netstat -tulpn' or 'ss -tulpn', or check if the server was started via 'blade server start' or similar.Affected if Chaosblade server mode is currently running and listening on a network port
-
Verify if the server endpoint is network-accessibleAttempt to access the server endpoint locally (e.g., curl http://localhost:3658 or the configured port) or check firewall rules and network configuration to determine if the port accepts remote connections.Affected if The server port is exposed to untrusted networks or is publicly accessible
-
Test for unauthenticated command injectionSend a request to the server endpoint with a cmd parameter (e.g., curl 'http://<server>:<port>/exec?cmd=whoami') without providing any authentication credentials.Affected if The server accepts and executes the cmd parameter without requiring authentication
A system is affected if Chaosblade version 0.3-1.7.3 is installed and running in server mode with the endpoint accessible over a network without authentication.
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.
dbcve · scopedEnable authentication for Chaosblade server mode and restrict network access to trusted sources. If authentication is not available in the version in use, upgrade to a patched version. Consider network segmentation to limit exposure.
Chaosblade version 1.7.4 or later
- 1. Stop any running Chaosblade server instances
- 2. Backup your current Chaosblade installation and configuration
- 3. Download the latest stable release of Chaosblade (version 1.7.4 or later) from the official GitHub repository: https://github.com/chaosblade-io/chaosblade/releases
- 4. Replace the existing chaosblade binary with the new version
- 5. Review and configure authentication settings if introduced in the update
- 6. Restart the Chaosblade server
- 7. Verify the server is running correctly and test that command execution requires proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47105 — 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-2023-47105 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