-
Notifications
You must be signed in to change notification settings - Fork 193
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
Compute all transitive aliases for OSV entries #1569
Comments
In-progress assessment:
On the face of it, this looks like it may be incomplete version enumeration for GHSA-2qmj-7962-cjq8, but further investigation is required. |
Can you clarify what the mismatch is? This seems like a issue with GHSA not updating their The API only returns the PYSEC entry, since 0.0.222 < 0.0.266, so according to the GHSA entry, 0.0.266 is not affected. |
Created github/advisory-database#2640 to resolve this upstream. |
Thanks @another-rex, I think I understand. I was expecting to see all aliases of the CVE related to version 0.0.266 |
We currently are working on a solution to populate the aliases field with all the aliases of the CVE. (Part of #1293) The API will still return the advisory that's affecting the version of the package you pass in (e.g. PYSEC-123), but at least the |
Add an alias computation cron job to solve issues like #1569.
It seems like when I search CVE-2023-36258 I got to results - PYSEC & GHSA:
![image](https://private-user-images.githubusercontent.com/112797342/261786594-26a877c6-fa22-424e-8572-175cc12bfb69.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNDM5NDYsIm5iZiI6MTczOTE0MzY0NiwicGF0aCI6Ii8xMTI3OTczNDIvMjYxNzg2NTk0LTI2YTg3N2M2LWZhMjItNDI0ZS04NTcyLTE3NWNjMTJiZmI2OS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwOVQyMzI3MjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iNjlhMzQyN2FkMzE1MDUyNjNkYmQwMzgzOGUwMDc4N2QxN2ExZGE4ZWIwMzQ0MjEyYmRiMmE3MDJhMzA2Nzk0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.OqxC3TgC9olg3F2EXIwCUCnPffGbOjcZzroGdUDijMg)
but when I search in the API:
I got only the PYSEC entry:
It means a lot because it seems like for
![image](https://private-user-images.githubusercontent.com/112797342/261786549-106fab25-4fb7-46c6-8dba-e2aa5a4995ec.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNDM5NDYsIm5iZiI6MTczOTE0MzY0NiwicGF0aCI6Ii8xMTI3OTczNDIvMjYxNzg2NTQ5LTEwNmZhYjI1LTRmYjctNDZjNi04ZGJhLWUyYWE1YTQ5OTVlYy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwOVQyMzI3MjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jOTVhNjc3NzAzOTQ3ZWJiNmVjOWYyZjcyOWZhMzNiYTAxMWUxZTgyOTk2NDljNjY3ZDZkNzM2NWEwNzkwNDYwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.c_uligojQu5z_OpbKaBn_sLYwvP0nCnrrYuQXPAeDWA)
langchain
the vulnerabilities in PYSEC are never fixed:While in GHSA they are (or at least include the 'last affected version':
![image](https://private-user-images.githubusercontent.com/112797342/261786529-b35a72c0-2a0c-4ec6-8c6d-be62aa0f8e44.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNDM5NDYsIm5iZiI6MTczOTE0MzY0NiwicGF0aCI6Ii8xMTI3OTczNDIvMjYxNzg2NTI5LWIzNWE3MmMwLTJhMGMtNGVjNi04YzZkLWJlNjJhYTBmOGU0NC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjA5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIwOVQyMzI3MjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wNzA2MmFhZmNhZDI0NWNkN2JiMDAxOTE4OTQ3NDA5OTdlODQyZTI3ODJlMDgxNTZlMmM4ZWNkZmFhNjliZDFjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.m2XjcOChVTJhto8l9Fwjxx5SB-9eohYDdu9jAJh7LvE)
The text was updated successfully, but these errors were encountered: