Skip to content
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

HTTP 500 or 504 errors when priority filtering is set to critical in https://ubuntu.com/security/cves #14577

Open
wapsi opened this issue Dec 16, 2024 · 1 comment

Comments

@wapsi
Copy link

wapsi commented Dec 16, 2024

Summary

If I go to URL: https://ubuntu.com/security/cves?version=noble&version=jammy&version=focal&version=bionic&version=xenial&version=trusty and check the "Ubuntu priority" to "Critical" and press "Apply filters", I'll receive "500: Server error" or "504 Gateway Time-out" page:

image

image

image

Steps to reproduce the behavior

  1. Go to URL: https://ubuntu.com/security/cves?version=noble&version=jammy&version=focal&version=bionic&version=xenial&version=trusty
  2. check the "Ubuntu priority" to "Critical"
  3. Press "Apply filters" button

Expected behavior

It should list all critical severity CVEs

Browser/device details

Browser: Curl 7.29.0 (x86_64-redhat-linux-gnu) or Firefox 133.0.3
OS: RHEL 7, Debian 12

Reported from

GitHub

@wapsi wapsi changed the title HTTP 500 or 504 errors when priority filtering is set to critical HTTP 500 or 504 errors when priority filtering is set to critical in https://ubuntu.com/security/cves Dec 16, 2024
@brlin-tw
Copy link

brlin-tw commented Dec 18, 2024

I can also reproduce this issue by opening the https://ubuntu.com/security/cves page, input anything in the "CVE ID or description contains:" input box, and hitting the green Search button on the right side.

Workarounds

Input nothing will bring you to the Search CVE reports page without errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants