Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact The primary use case for Smokescreen is to prevent server-side request forgery (SSRF) attacks in which external attackers leverage the behavior of applications to connect to or scan internal infrastructure. Smokescreen also offers an option to deny access to additional (e.g., external) URLs by way of a deny list. There was an issue in Smokescreen that made it possible to bypass the deny list feature by surrounding the hostname with square brackets (e.g. [example.com]). Recommendation Upgrade Smokescreen to version 0.0.4 or later. Acknowledgements Thanks to Axel Chong for reporting the issue. For more information Email us at security@stripe.com
Recommended action: Upgrade to 0.0.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The primary use case for Smokescreen is to prevent server-side request forgery (SSRF) attacks in which external attackers leverage the behavior of applications to connect to or scan internal infrastructure. Smokescreen also offers an option to deny access to additional (e.g., external) URLs by way of a deny list. There was an issue in Smokescreen that made it possible to bypass the deny list feature by appending a dot to the end of user-supplied URLs, or by providing input in a different letter case. Recommendation Upgrade Smokescreen to version 0.0.3 or later. Acknowledgements Thanks to Grzegorz Niedziela for reporting the issue. For more information Email us at security@stripe.com
Recommended action: Upgrade to 0.0.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.