You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there people! I have a situation here...
Since the vulnerable fix version was created with the same version number as it were before the vulnerability fix, some vulnerability checkers (nvd.nist.gov) are still considering as a broken version.
Would be a problem to generate a fix version with different number? 3.3.1 & 6.3.1 https://nvd.nist.gov/vuln/detail/CVE-2024-45296
The text was updated successfully, but these errors were encountered:
No, the fixes were already released. This would need to be fixed in the vulnerability checker since I don't see how releasing another version would fix this now.
Since the vulnerable fix version was created with the same version number as it were before the vulnerability fix
This isn't possible if I'm reading this correctly. You can't release the same version with different code multiple times. The fixes were released a minor versions.
Hey there people! I have a situation here...
Since the vulnerable fix version was created with the same version number as it were before the vulnerability fix, some vulnerability checkers (nvd.nist.gov) are still considering as a broken version.
Would be a problem to generate a fix version with different number? 3.3.1 & 6.3.1
https://nvd.nist.gov/vuln/detail/CVE-2024-45296
The text was updated successfully, but these errors were encountered: