-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Added sarif template * Updated readme * fixed tests * Added integration tests and fixed all sarif validations issues * Added tests for endWithPeriod * Fixed tests, and added sarif golden file * removed optional newline sequence
- Loading branch information
Showing
6 changed files
with
226 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,64 @@ | ||
| { | ||
| "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", | ||
| "version": "2.1.0", | ||
| "runs": [ | ||
| { | ||
| "tool": { | ||
| "driver": { | ||
| "name": "Trivy: Vulnerability Scanner for Containers", | ||
| "rules": [ | ||
| {{- $t_first := true }} | ||
| {{- range . }} | ||
| {{- range .Vulnerabilities -}} | ||
| {{- if $t_first -}} | ||
| {{- $t_first = false -}} | ||
| {{ else -}} | ||
| , | ||
| {{- end }} | ||
| { | ||
| "id": "[{{ .Vulnerability.Severity }}] {{ .VulnerabilityID }}", | ||
| "name": "container_scanning", | ||
| "shortDescription": { | ||
| "text": {{ printf "error found in package %s." (print .PkgName .Title ) | printf "%q" }} | ||
| }, | ||
| "fullDescription": { | ||
| "text": {{ endWithPeriod .Description | printf "%q" }} | ||
| }, | ||
| "defaultConfiguration": null, | ||
| "properties": { | ||
| "tags": [ | ||
| "{{ .PkgName }}" | ||
| ], | ||
| "precision": "very-high" | ||
| } | ||
| } | ||
| {{- end -}} | ||
| {{- end -}} | ||
| ] | ||
| } | ||
| }, | ||
| "results": [ | ||
| {{- $t_first := true }} | ||
| {{- range . }} | ||
| {{- range $index, $vulnerability := .Vulnerabilities -}} | ||
| {{- if $t_first -}} | ||
| {{- $t_first = false -}} | ||
| {{ else -}} | ||
| , | ||
| {{- end }} | ||
| { | ||
| "ruleId": "[{{ $vulnerability.Vulnerability.Severity }}] {{ $vulnerability.VulnerabilityID }}", | ||
| "ruleIndex": {{ $index }}, | ||
| "level": "error", | ||
| "message": { | ||
| "text": {{ endWithPeriod $vulnerability.Description | printf "%q" }} | ||
| }, | ||
| "locations": [] | ||
| } | ||
| {{- end -}} | ||
| {{- end -}} | ||
| ], | ||
| "columnKind": "utf16CodeUnits" | ||
| } | ||
| ] | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,120 @@ | ||
| { | ||
| "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", | ||
| "version": "2.1.0", | ||
| "runs": [ | ||
| { | ||
| "tool": { | ||
| "driver": { | ||
| "name": "Trivy: Vulnerability Scanner for Containers", | ||
| "rules": [ | ||
| { | ||
| "id": "[MEDIUM] CVE-2019-1549", | ||
| "name": "container_scanning", | ||
| "shortDescription": { | ||
| "text": "error found in package opensslopenssl: information disclosure in fork()." | ||
| }, | ||
| "fullDescription": { | ||
| "text": "OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c)." | ||
| }, | ||
| "defaultConfiguration": null, | ||
| "properties": { | ||
| "tags": [ | ||
| "openssl" | ||
| ], | ||
| "precision": "very-high" | ||
| } | ||
| }, | ||
| { | ||
| "id": "[MEDIUM] CVE-2019-1551", | ||
| "name": "container_scanning", | ||
| "shortDescription": { | ||
| "text": "error found in package opensslopenssl: Integer overflow in RSAZ modular exponentiation on x86_64." | ||
| }, | ||
| "fullDescription": { | ||
| "text": "There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t)." | ||
| }, | ||
| "defaultConfiguration": null, | ||
| "properties": { | ||
| "tags": [ | ||
| "openssl" | ||
| ], | ||
| "precision": "very-high" | ||
| } | ||
| }, | ||
| { | ||
| "id": "[MEDIUM] CVE-2019-1563", | ||
| "name": "container_scanning", | ||
| "shortDescription": { | ||
| "text": "error found in package opensslopenssl: information disclosure in PKCS7_dataDecode and CMS_decrypt_set1_pkey." | ||
| }, | ||
| "fullDescription": { | ||
| "text": "In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s)." | ||
| }, | ||
| "defaultConfiguration": null, | ||
| "properties": { | ||
| "tags": [ | ||
| "openssl" | ||
| ], | ||
| "precision": "very-high" | ||
| } | ||
| }, | ||
| { | ||
| "id": "[LOW] CVE-2019-1547", | ||
| "name": "container_scanning", | ||
| "shortDescription": { | ||
| "text": "error found in package opensslopenssl: side-channel weak encryption vulnerability." | ||
| }, | ||
| "fullDescription": { | ||
| "text": "Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s)." | ||
| }, | ||
| "defaultConfiguration": null, | ||
| "properties": { | ||
| "tags": [ | ||
| "openssl" | ||
| ], | ||
| "precision": "very-high" | ||
| } | ||
| }] | ||
| } | ||
| }, | ||
| "results": [ | ||
| { | ||
| "ruleId": "[MEDIUM] CVE-2019-1549", | ||
| "ruleIndex": 0, | ||
| "level": "error", | ||
| "message": { | ||
| "text": "OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c)." | ||
| }, | ||
| "locations": [] | ||
| }, | ||
| { | ||
| "ruleId": "[MEDIUM] CVE-2019-1551", | ||
| "ruleIndex": 1, | ||
| "level": "error", | ||
| "message": { | ||
| "text": "There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t)." | ||
| }, | ||
| "locations": [] | ||
| }, | ||
| { | ||
| "ruleId": "[MEDIUM] CVE-2019-1563", | ||
| "ruleIndex": 2, | ||
| "level": "error", | ||
| "message": { | ||
| "text": "In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s)." | ||
| }, | ||
| "locations": [] | ||
| }, | ||
| { | ||
| "ruleId": "[LOW] CVE-2019-1547", | ||
| "ruleIndex": 3, | ||
| "level": "error", | ||
| "message": { | ||
| "text": "Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s)." | ||
| }, | ||
| "locations": [] | ||
| }], | ||
| "columnKind": "utf16CodeUnits" | ||
| } | ||
| ] | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters