7 matches found
CLEANSTART-2026-QN19137 httpTokenCacheKey uses path
Security vulnerability affects the nfs-subdir-external-provisioner package. httpTokenCacheKey uses path...
PT-2026-122804
Security vulnerability affects the nfs-subdir-external-provisioner package. httpTokenCacheKey uses path...
CVE-2022-30636
httpTokenCacheKey uses path.Base to extract the expected HTTP-01 token value to lookup in the DirCache implementation. On Windows, path.Base acts differently to filepath.Base, since Windows uses a different path separator \ vs. /, allowing a user to provide a relative path, i.e...
CVE-2022-30636
httpTokenCacheKey uses path.Base to extract the expected HTTP-01 token value to lookup in the DirCache implementation. On Windows, path.Base acts differently to filepath.Base, since Windows uses a different path separator \ vs. /, allowing a user to provide a relative path, i.e...
CVE-2022-30636
httpTokenCacheKey uses path.Base to extract the expected HTTP-01 token value to lookup in the DirCache implementation. On Windows, path.Base acts differently to filepath.Base, since Windows uses a different path separator \ vs. /, allowing a user to provide a relative path, i.e...
CVE-2022-30636
httpTokenCacheKey uses path.Base to extract the expected HTTP-01 token value to lookup in the DirCache implementation. On Windows, path.Base acts differently to filepath.Base, since Windows uses a different path separator \ vs. /, allowing a user to provide a relative path, i.e...
CVE-2022-30636
The httpTokenCacheKey function is vulnerable to a path traversal issue because it uses path.Base to extract HTTP-01 token values. On Windows systems, path.Base behaves differently than filepath.Base regarding path separators, allowing a user to provide a relative path (e.g., .well-known/acme-chal...