-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
False positive on the PostgreSQL JDBC client JAR #1529
Comments
This was fixed recently - see #1488 - but apparently pops up again. There are multiple problems with this:
I’d definitely look at the latter in any case, since that shows that the Maven plugin somehow does not work correctly!
|
It appears that the CVE was updated recently to add Additionally, we have taken the stance on DB related findings that we would only suppress specific CVEs as they are reported/found as opposed to just suppressing the CPE. The reason is that suppressing by CPE will remove all future CVEs where as just suppressing by CVE will still match on new/un-reviewed findings and it is possible that one of these would affect the driver and still be listed under the database server's CPE. |
@jeremylong That all sounds reasonable ... we've suppressed it locally for now but let me know if we can help with the conversion to JSON, etc. |
On Wed, 24 Oct 2018, Jeremy Long wrote:
opposed to just suppressing the CPE. The reason is that suppressing by
CPE will remove all future CVEs where as just suppressing by CVE will
still match on new/un-reviewed findings and it is possible that one of
these would affect the driver and still be listed under the database
server's CPE.
I doubt: the JDBC has cpe:/a:postgresql:postgresql_jdbc_driver
and you could ask the PostgreSQL team whether they intend to
keep them separated.
Additionally, we have taken the stance on DB related findings that we
would only suppress specific CVEs as they are reported/found as
Then please explain to me how this is a “DB related finding” when
your plugin is unable to realise that version 42.x is not affected
by something affecting only some 9.x releases?
|
@mirabilos you are more than welcome to go use another product in this space - no need to be rude to maintainers.
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
CVE-2016-7048 was updated on 2018-10-12 and is now breaking our builds. Upon further inspection, we see that this is a vulnerability to those using the interactive installer - clearly those of us downloading this artifact from Maven Central are not affected
False positive on library postgresql.jar - reported as
cpe:2.3:a:postgresql:postgresql:9.3
- CVE-2016-7048At least versions >= 42.2.1 are affected.
The text was updated successfully, but these errors were encountered: