What is CVE-2023-33965?

CVE-2023-33965 is a critical-severity OS command injection vulnerability in github.com/txthinking/brook (go), affecting versions < 20230606. It is fixed in 20230606. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

How severe is CVE-2023-33965?

CVE-2023-33965 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/txthinking/brook are affected by CVE-2023-33965?

github.com/txthinking/brook (go) versions < 20230606 is affected.

Is there a fix for CVE-2023-33965?

Yes. CVE-2023-33965 is fixed in 20230606. Upgrade to this version or later.

Is CVE-2023-33965 exploitable, and should I be worried?

Whether CVE-2023-33965 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-33965 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-33965 in github.com/txthinking/brook

Q: How severe is CVE-2023-33965?

CVE-2023-33965 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/txthinking/brook are affected by CVE-2023-33965?

github.com/txthinking/brook (go) versions < 20230606 is affected.

Q: Is there a fix for CVE-2023-33965?

Yes. CVE-2023-33965 is fixed in 20230606. Upgrade to this version or later.

Q: Is CVE-2023-33965 exploitable, and should I be worried?

Whether CVE-2023-33965 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-33965 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-33965?

Upgrade github.com/txthinking/brook to 20230606 or later.

Summary

Brook's tproxy server is vulnerable to a drive-by command injection.

The tproxy server is vulnerable to a drive-by command injection. An attacker may fool a victim into visiting a malicious web page which will trigger requests to the local tproxy service leading to remote code execution.

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2023-33965 has a CVSS score of 9.6 (Critical). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (20230606); upgrading removes the vulnerable code path.

Affected versions

github.com/txthinking/brook (< 20230606)

Security releases

github.com/txthinking/brook → 20230606 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/txthinking/brook to 20230606 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-33965? CVE-2023-33965 is a critical-severity OS command injection vulnerability in github.com/txthinking/brook (go), affecting versions < 20230606. It is fixed in 20230606. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
How severe is CVE-2023-33965? CVE-2023-33965 has a CVSS score of 9.6 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/txthinking/brook are affected by CVE-2023-33965? github.com/txthinking/brook (go) versions < 20230606 is affected.
Is there a fix for CVE-2023-33965? Yes. CVE-2023-33965 is fixed in 20230606. Upgrade to this version or later.
Is CVE-2023-33965 exploitable, and should I be worried? Whether CVE-2023-33965 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-33965 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-33965? Upgrade github.com/txthinking/brook to 20230606 or later.