https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 09 Oct 2026 08:24:42 +0000 https://cve.radiocsirt.org/vuln/cnvd-2020-29879 cnvd-2020-29879 https://cve.radiocsirt.org/vuln/cnvd-2020-29879 https://cve.radiocsirt.org/vuln/euvd-2026-36516 EUVD-2026-36516 https://cve.radiocsirt.org/vuln/euvd-2026-36516 https://cve.radiocsirt.org/vuln/fkie_cve-2020-5274 <p>In Symfony before versions 5.0.5 and 4.4.5, some properties of the Exception were not properly escaped when the `ErrorHandler` rendered it stacktrace. In addition, the stacktrace were displayed even in a non-debug configuration. The ErrorHandler now escape alls properties of the exception, and the stacktrace is only display in debug configuration. This issue is patched in symfony/http-foundation versions 4.4.5 and 5.0.5</p> <p>In Symfony before versions 5.0.5 and 4.4.5, some properties of the Exception were not properly escaped when the `ErrorHandler` rendered it stacktrace. In addition, the stacktrace were displayed even in a non-debug configuration. The ErrorHandler now escape alls properties of the exception, and the stacktrace is only display in debug configuration. This issue is patched in symfony/http-foundation versions 4.4.5 and 5.0.5</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-5274 https://cve.radiocsirt.org/vuln/ghsa-m884-279h-32v2 <p><strong>Affected:</strong> Packagist: symfony/error-handler, Packagist: symfony/symfony</p> <p>Description -----------</p> <p>When `ErrorHandler` renders an exception HTML page, it uses un-escaped properties from the related Exception class to render the stacktrace. The security issue comes from the fact that the stacktraces were also displayed in non-`debug` environments.</p> <p>Resolution ----------</p> <p>The `ErrorHandler` class now escapes all properties coming from the related Exception, and the stacktrace is not displayed anymore in non-`debug` environments.</p> <p>The patches for this issue are available [here](https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad) and [here](https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db) for branch 4.4.</p> <p>Credits -------</p> <p>I would like to thank Luka Sikic for reporting &amp; Yonel Ceruto and Jérémy Derussé for fixing the issue.</p> <p><strong>Affected:</strong> Packagist: symfony/error-handler, Packagist: symfony/symfony</p> <p>Description -----------</p> <p>When `ErrorHandler` renders an exception HTML page, it uses un-escaped properties from the related Exception class to render the stacktrace. The security issue comes from the fact that the stacktraces were also displayed in non-`debug` environments.</p> <p>Resolution ----------</p> <p>The `ErrorHandler` class now escapes all properties coming from the related Exception, and the stacktrace is not displayed anymore in non-`debug` environments.</p> <p>The patches for this issue are available [here](https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad) and [here](https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db) for branch 4.4.</p> <p>Credits -------</p> <p>I would like to thank Luka Sikic for reporting &amp; Yonel Ceruto and Jérémy Derussé for fixing the issue.</p> https://cve.radiocsirt.org/vuln/ghsa-m884-279h-32v2 https://cve.radiocsirt.org/vuln/gsd-2020-5274 gsd-2020-5274 https://cve.radiocsirt.org/vuln/gsd-2020-5274