Java: Additional hardcoded credentials candidates 3rd-party api calls #6716
Conversation
|
I can provide at least one valid result from each of the added services/libs but as these are credential disclosure issues, I would like to do that through a private channel. |
|
Should I move this into an experimental query? |
|
This is straightforward enough that assuming seclab can confirm the results are reasonable I'd be happy to take it straight into the non-experimental library |
I already have an issue open for this github/securitylab#432, just need to know about the best way to provide the seclab with the results as they contain potentially confidential information. |
|
Please add to the tests in Please add a change note in |
|
Will sure do @smowton. I should push the changes in the next couple of days. |


Included the methods that might receive hard-coded credential material in their parameters from some of the most used SSH, FTP, and MongoDB Java libraries in the Maven official repository to the SensitiveApi.qll library.
The text was updated successfully, but these errors were encountered: