-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
7 High Security vulnerability on latest CSI-attacher:v4.3.0 sidecar image #459
Comments
What happened:
The following 7 high severity CVEs, which are listed in the prisma cloud's container image scan report and they were just released along with CSI powerflex version 2.7.0. Are there any solutions for these vulnerabilities flagged against "csi-attacher:v4.3.0" sidecar image ? If anyone encounters these vulnerabilities , Please provide advice on how to address these vulnerabilities. What you expected to happen: How to reproduce it: K8s version used Scanning Tool Used: Prisma Cloud |
/assign |
Thanks @praveenkprabhakaran for reporting these. From my point of view, only CVE-2023-29403 might be meaningful in the context of the execution of the external-attacher. Once that PR is merged kubernetes-csi/csi-release-tools#231 ; the future releases of the CSI sidecars won't be affected by above CVEs. |
Good day all, CVE-2023-29406 Please let me know if you need more info. |
We have released updated versions of v4.4.x to address CVE issues. I would recommend upgrading to the latest. Unfortunately CVE patching is a manual process and if you need fixes for older supported minors please send PRs. |
/close |
@jsafrane: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The following 7 high severity CVEs, which are listed in the prisma cloud's container image scan report and they were just released along with CSI powerflex version 2.7.0. Are there any solutions for these vulnerabilities flagged against "csi-attacher:v4.3.0" sidecar image ? If anyone encounters these vulnerabilities , Please provide advice on how to address these vulnerabilities.
CVE-2023-29400
CVE-2023-29405
CVE-2023-24540
CVE-2023-29404
CVE-2023-24539
CVE-2023-29403
CVE-2023-29402
Detailed description of above CVEs:-
"CVE-2023-29400": [
{
"cve": "CVE-2023-29400",
"packageName": "go",
"packageVersion": "1.20.3",
"severity": "High",
"actionable": true,
"fixedInVersion": "fixed in 1.20.4, 1.19.9",
"fixDate": 1684793000,
"desc": "Templates containing actions in unquoted HTML attributes (e.g. \"attr={{.}}\") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.",
"type": "image",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2023-29400"
}
],
"CVE-2023-29405": [
{
"cve": "CVE-2023-29405",
"packageName": "go",
"packageVersion": "1.20.3",
"severity": "High",
"actionable": true,
"fixedInVersion": "fixed in 1.20.5, 1.19.10",
"fixDate": 1686927000,
"desc": "The go command may execute arbitrary code at build time when using cgo. This may occur when running \"go get\" on a malicious module, or when running any other command which builds untrusted code. This is can by triggered by linker flags, specified via a \"#cgo LDFLAGS\" directive. Flags containing embedded spaces are mishandled, allowing disallowed flags to be smuggled through the LDFLAGS sanitization by including them in the argument of another flag. This only affects usage of the gccgo compiler.",
"type": "image",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2023-29405"
}
],
"CVE-2023-24540": [
{
"cve": "CVE-2023-24540",
"packageName": "go",
"packageVersion": "1.20.3",
"severity": "High",
"actionable": true,
"fixedInVersion": "fixed in 1.20.4, 1.19.9",
"fixDate": 1684793000,
"desc": "Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set \"\\t\n\\f\r\\u0020\\u2028\\u2029\" in JavaScript contexts that also contain actions may not be properly sanitized during execution.",
"type": "image",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2023-24540"
}
],
"CVE-2023-29404": [
{
"cve": "CVE-2023-29404",
"packageName": "go",
"packageVersion": "1.20.3",
"severity": "High",
"actionable": true,
"fixedInVersion": "fixed in 1.20.5, 1.19.10",
"fixDate": 1686927000,
"desc": "The go command may execute arbitrary code at build time when using cgo. This may occur when running \"go get\" on a malicious module, or when running any other command which builds untrusted code. This is can by triggered by linker flags, specified via a \"#cgo LDFLAGS\" directive. The arguments for a number of flags which are non-optional are incorrectly considered optional, allowing disallowed flags to be smuggled through the LDFLAGS sanitization. This affects usage of both the gc and gccgo compilers.",
"type": "image",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2023-29404"
}
],
"CVE-2023-24539": [
{
"cve": "CVE-2023-24539",
"packageName": "go",
"packageVersion": "1.20.3",
"severity": "High",
"actionable": true,
"fixedInVersion": "fixed in 1.20.4, 1.19.9",
"fixDate": 1684793000,
"desc": "Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a \'/\' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.",
"type": "image",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2023-24539"
}
],
"CVE-2023-29403": [
{
"cve": "CVE-2023-29403",
"packageName": "go",
"packageVersion": "1.20.3",
"severity": "High",
"actionable": true,
"fixedInVersion": "fixed in 1.20.5, 1.19.10",
"fixDate": 1686899000,
"desc": "On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors. If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.",
"type": "image",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2023-29403"
}
],
"CVE-2023-29402": [
{
"cve": "CVE-2023-29402",
"packageName": "go",
"packageVersion": "1.20.3",
"severity": "High",
"actionable": true,
"fixedInVersion": "fixed in 1.20.5, 1.19.10",
"fixDate": 1686942000,
"desc": "The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when running a go program which uses cgo. This may occur when running an untrusted module which contains directories with newline characters in their names. Modules which are retrieved using the go command, i.e. via \"go get\", are not affected (modules retrieved using GOPATH-mode, i.e. GO111MODULE=off, may be affected).",
"type": "image",
"link": "https://nvd.nist.gov/vuln/detail/CVE-2023-29402"
}
]
},
The text was updated successfully, but these errors were encountered: