Vulnerability of dependency "github.com/opencontainers/runc"

[Silence-worker-02]

Hello, we are a team researching the dependency management mechanism of Golang. During our analysis, we came across your project and noticed that it contains a vulnerability (CVE-2022-29162). In your project, the github.com/opencontainers/runc package is being used at version github.com/opencontainers/runc v1.0.2, but the patched version is v1.1.2. To fix the vulnerability, we recommend modifying the go.mod file to update the version to v1.1.2 or higher. Thank you for your attention to this matter.

[kcq]

Do you have an exploit or, at least, a sequence diagram for it that shows how that vulnerability can be triggered in slim?

[Silence-worker-02]

Thank you for reply. During our manual examination of the call graph, we found that 'github.com/opencontainers/runc' is imported by 'github.com/docker/docker', but the vulnerable function is not utilized in the latter. Nevertheless, to proactively mitigate potential future risks, we strongly recommend upgrading 'github.com/opencontainers/runc' to its patch version. This precautionary measure ensures that the vulnerability is addressed and reduces any potential security risks in the long term.

[kcq]

Fixing just in case isn't a great approach and it blurs the line between real vulnerabilities and software that's simply vulnerability adjacent. As an industry we need to focus on the real and exploitable vulnerabilities otherwise there'll be too much noise and vulnerability fatigue.

I do appreciate the report though! Thank you for opening the issue.