CVE-2024-43798
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 · uneditedChisel is a fast TCP/UDP tunnel, transported over HTTP, secured via SSH. The Chisel server doesn't ever read the documented `AUTH` environment variable used to set credentials, which allows any unauthenticated user to connect, even if credentials were set. Anyone running the Chisel server that is using the `AUTH` environment variable to specify credentials to authenticate against is affected by this vulnerability. Chisel is often used to provide an entrypoint to a private network, which means services that are gated by Chisel may be affected. Additionally, Chisel is often used for exposing services to the internet. An attacker could MITM requests by connecting to a Chisel server and requesting to forward traffic from a remote port. This issue has been addressed in release version 1.10.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.
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 confidenceThe Chisel server fails to read the documented `AUTH` environment variable used to set authentication credentials, effectively bypassing all configured authentication. This allows any unauthenticated user to connect to the server. An attacker could exploit this to perform MITM attacks by connecting to the server and requesting to forward traffic from remote ports.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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 Chisel is installedRun `chisel --version` or check for the chisel binary in common paths like `/usr/bin/chisel`, `$(go env GOPATH)/bin/chisel`, or via package managers.Affected if Chisel is installed and the version is below 1.10.0 (or cannot be determined to be 1.10.0 or later)
-
Check running Chisel server processesUse `ps aux | grep chisel` or `pgrep -a chisel` to identify if a Chisel server process is currently running.Affected if A Chisel server process is running from a vulnerable version (< 1.10.0)
-
Verify the AUTH environment variable configurationInspect the environment of running chisel processes with `ps eww <pid>` (Linux) or check how the service was started (systemd environment file, docker env, shell script). Look for the presence of the AUTH variable.Affected if The AUTH variable is set but the Chisel version is vulnerable, indicating authentication is non-functional
-
Confirm server is network-accessibleCheck if the chisel server is bound to a network interface (0.0.0.0 or specific IP) using `netstat -tlnp | grep chisel` or `ss -tlnp | grep chisel`.Affected if The server is exposed on a network interface and runs a vulnerable version, meaning unauthenticated attackers can connect
You are affected if you run any version of Chisel server older than 1.10.0, regardless of whether the AUTH environment variable is configured.
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 · scopedUpgrade to Chisel version 1.10.0 or later immediately. There are no known workarounds; the `AUTH` environment variable is non-functional in vulnerable versions.
1.10.0
- 1. Identify the current Chisel version currently installed (e.g., chisel --version)
- 2. Navigate to the official Chisel releases page at https://github.com/jpillora/chisel/releases
- 3. Download the release package for version 1.10.0 matching your operating system and architecture
- 4. Replace the existing chisel binary with the new version 1.10.0 binary
- 5. Restart the Chisel server to apply the updated binary
- 6. Verify the new version is running (chisel --version)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43798 — 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-2024-43798 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