What is GHSA-VV6C-69R6-CHG9?

GHSA-VV6C-69R6-CHG9 is a low-severity security vulnerability in github.com/landlock-lsm/go-landlock (go), affecting versions >= 0.0.0-20240109, < 0.0.0-20241013234402-fb3ad845df46. It is fixed in 0.0.0-20241013234402-fb3ad845df46.

Which versions of github.com/landlock-lsm/go-landlock are affected by GHSA-VV6C-69R6-CHG9?

github.com/landlock-lsm/go-landlock (go) versions >= 0.0.0-20240109, < 0.0.0-20241013234402-fb3ad845df46 is affected.

Is there a fix for GHSA-VV6C-69R6-CHG9?

Yes. GHSA-VV6C-69R6-CHG9 is fixed in 0.0.0-20241013234402-fb3ad845df46. Upgrade to this version or later.

Is GHSA-VV6C-69R6-CHG9 exploitable, and should I be worried?

Whether GHSA-VV6C-69R6-CHG9 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 GHSA-VV6C-69R6-CHG9 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 GHSA-VV6C-69R6-CHG9?

Upgrade github.com/landlock-lsm/go-landlock to 0.0.0-20241013234402-fb3ad845df46 or later.

GHSA-VV6C-69R6-CHG9

Q: Which versions of github.com/landlock-lsm/go-landlock are affected by GHSA-VV6C-69R6-CHG9?

github.com/landlock-lsm/go-landlock (go) versions >= 0.0.0-20240109, < 0.0.0-20241013234402-fb3ad845df46 is affected.

Q: Is there a fix for GHSA-VV6C-69R6-CHG9?

Yes. GHSA-VV6C-69R6-CHG9 is fixed in 0.0.0-20241013234402-fb3ad845df46. Upgrade to this version or later.

Q: Is GHSA-VV6C-69R6-CHG9 exploitable, and should I be worried?

Whether GHSA-VV6C-69R6-CHG9 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 GHSA-VV6C-69R6-CHG9 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 GHSA-VV6C-69R6-CHG9?

Upgrade github.com/landlock-lsm/go-landlock to 0.0.0-20241013234402-fb3ad845df46 or later.

Summary

Go-Landlock in best-effort mode did not restrict TCP bind and connect operations correctly

Workarounds

None.

References

Currently none.

The existing users of Go-Landlock on Github have the following bugs filed:

Impact

When using the recommended "best-effort" mode, Go-Landlock did not restrict the TCP bind() and connect() operations any more when they were requested. This affects Go-Landlock users to whom both of the following conditions apply:

They use Landlock rulesets that are supposed to restrict networking (through landlock.V4, landlock.V5, or self-configured).
These Landlock rulesets are used in best-effort mode.

Typically, affected code uses the Go-Landlock API like this (the crucial part being the combination of V4/V5 and .BestEffort()):

err := landlock.V5.BestEffort().Restrict(...)

This is a bug in the Go-Landlock library and does not affect programs that use Landlock via C or other language bindings.
The bug only affects networking restrictions. File system restrictions continue to work as expected.

Affected versions

github.com/landlock-lsm/go-landlock (>= 0.0.0-20240109, < 0.0.0-20241013234402-fb3ad845df46)

Security releases

github.com/landlock-lsm/go-landlock → 0.0.0-20241013234402-fb3ad845df46 (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

Patched in: https://github.com/landlock-lsm/go-landlock/commit/fb3ad845df462d013f9c8a965c496617c6a5778b
Users should upgrade to: v0.0.0-20241013234402-fb3ad845df46

Go package dependencies can be updated using go get -u from the project directory.

Projects on Github might get notified by Dependabot, once this advisory is public.

Frequently Asked Questions

What is GHSA-VV6C-69R6-CHG9? GHSA-VV6C-69R6-CHG9 is a low-severity security vulnerability in github.com/landlock-lsm/go-landlock (go), affecting versions >= 0.0.0-20240109, < 0.0.0-20241013234402-fb3ad845df46. It is fixed in 0.0.0-20241013234402-fb3ad845df46.
Which versions of github.com/landlock-lsm/go-landlock are affected by GHSA-VV6C-69R6-CHG9? github.com/landlock-lsm/go-landlock (go) versions >= 0.0.0-20240109, < 0.0.0-20241013234402-fb3ad845df46 is affected.
Is there a fix for GHSA-VV6C-69R6-CHG9? Yes. GHSA-VV6C-69R6-CHG9 is fixed in 0.0.0-20241013234402-fb3ad845df46. Upgrade to this version or later.
Is GHSA-VV6C-69R6-CHG9 exploitable, and should I be worried? Whether GHSA-VV6C-69R6-CHG9 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 GHSA-VV6C-69R6-CHG9 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 GHSA-VV6C-69R6-CHG9? Upgrade github.com/landlock-lsm/go-landlock to 0.0.0-20241013234402-fb3ad845df46 or later.