Incorrect mapping of Applicable versions for CVE-2023-28858 & CVE-2023-28859 #4473
Replies: 2 comments 6 replies
-
Did you see our checklist? The data source (GitHub Security Advisories) seems to be wrong. Please report it to GitHub. |
Beta Was this translation helpful? Give feedback.
-
Detailed explanation from Git lab attached below Both those advisories were updated last week to reflect NVD's change stating that the vulnerability only exists since version 4.2.0: https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/blob/master/pypi/redis/CVE-2023-28858.yml#L15 Therefore, is you are using the redis-py library version 2.x, GitLab should no longer flag it as being vulnerable. The previously detected vulnerability will continue to exist, but its state should change to "remediated" and "no longer detected". Note that you need to rerun the Dependency Scanning pipeline to get up-to-date results. |
Beta Was this translation helpful? Give feedback.
-
IDs
CVE-2023-28858 , CVE-2023-28859
Description
Hi Team ,
we have reported anomaly with CVEs in discussion title to be applicable for higher versions i.e with 4.x & not impacted with versions running with 2.x which is updated under https://avd.aquasec.com/nvd/2023/cve-2023-28859/ , https://avd.aquasec.com/nvd/2023/cve-2023-28858 respectively on May17th 2023 both in NVD and also AVD. Can we know when would these changes reflect in Trivy DB so that we no more see these as findings from trivy report for older versions of redis Metadata async library running with 2.10.6 , 2.25.1 (2.x) .Thanks in advance
Best
Sreecharan Guduri
Reproduction Steps
Target
Container Image
Scanner
Vulnerability
Target OS
Ubuntu 18.04
Debug Output
Version
Checklist
-f json
that shows data sources and confirmed that the security advisory in data sources was correctBeta Was this translation helpful? Give feedback.
All reactions