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

Use specific cpe-id on cvefor api cause memory leak #1043

Open
wang-fut opened this issue Jan 10, 2024 · 6 comments
Open

Use specific cpe-id on cvefor api cause memory leak #1043

wang-fut opened this issue Jan 10, 2024 · 6 comments
Labels

Comments

@wang-fut
Copy link

CPE ID: cpe:2.3:a:google:chrome::::::::

My env:
OS: RHEL 7 & 8
Build cve-search on Docker using "CVE Search Docker" project
Build number: 55b8795

Because I am using "CVE Search Docker" project,
there are 3 container exsit: cve-search, redis, mongo.
When I using the CPE ID on cvefor api,
the cve-search container will get tons of memory immediately
and finally cause the OOM Killer to reset container's memory.

@wang-fut
Copy link
Author

The CPE ID of Google Chrome without a specific version info has 3314 cveid matched at the moment.
Maybe cve-search couldn't handle them all at once.

@wang-fut
Copy link
Author

Even from the offical website, I cannot view the Google Chrome's cves
image

@P-T-I P-T-I added the bug label Jan 18, 2024
@P-T-I
Copy link
Member

P-T-I commented Jan 18, 2024

yeah; can definitely confirm this; the backend code doesn't really does a good job on result pagination.... It simply requests all off the entries, which in this case are simply too much... This needs to be fixed in future release (maybe specific cvexplore version); need quite a lot of re-write...

Copy link

Stale issue message

Copy link

Stale issue message

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2024
@oh2fih
Copy link
Contributor

oh2fih commented May 27, 2024

This is still an issue; should be reopened.

@P-T-I P-T-I reopened this May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants