Code
Testing D:\0_tmp\snyk\webgoat1 ...
✗ [Low] Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Path: JavaSource/org/owasp/webgoat/lessons/WeakSessionID.java, line 208
Info: Cookie misses a call to setSecure. Set the Secure flag to true to protect the cookie from man-in-the-middle attacks.
✗ [Low] Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 171
Info: Cookie misses a call to setSecure. Set the Secure flag to true to protect the cookie from man-in-the-middle attacks.
✗ [Low] Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 192
Info: Cookie misses a call to setSecure. Set the Secure flag to true to protect the cookie from man-in-the-middle attacks.
✗ [Low] Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Path: JavaSource/org/owasp/webgoat/lessons/WeakAuthenticationCookie.java, line 144
Info: Cookie misses a call to setSecure. Set the Secure flag to true to protect the cookie from man-in-the-middle attacks.
✗ [Low] Trust Boundary Violation
Path: JavaSource/org/owasp/webgoat/lessons/SQLInjection/ViewProfile.java, line 86
Info: Unsanitized input from an HTTP parameter flows into setAttribute where it is used to modify the HTTP session object. This could result in mixing trusted and untrusted data in the same data structure, thus increasing the likelihood to mistakenly trust unvalidated data.
✗ [Low] Trust Boundary Violation
Path: JavaSource/org/owasp/webgoat/lessons/SQLInjection/Login.java, line 154
Info: Unsanitized input from an HTTP parameter flows into setAttribute where it is used to modify the HTTP session object. This could result in mixing trusted and untrusted data in the same data structure, thus increasing the likelihood to mistakenly trust unvalidated data.
✗ [Low] Trust Boundary Violation
Path: JavaSource/org/owasp/webgoat/lessons/SQLInjection/Login.java, line 196
Info: Unsanitized input from an HTTP parameter flows into setAttribute where it is used to modify the HTTP session object. This could result in mixing trusted and untrusted data in the same data structure, thus increasing the likelihood to mistakenly trust unvalidated data.
✗ [Low] Trust Boundary Violation
Path: JavaSource/org/owasp/webgoat/lessons/CrossSiteScripting/FindProfile.java, line 84
Info: Unsanitized input from an HTTP parameter flows into setAttribute where it is used to modify the HTTP session object. This could result in mixing trusted and untrusted data in the same data structure, thus increasing the likelihood to mistakenly trust unvalidated data.
✗ [Low] Use of Password Hash With Insufficient Computational Effort
Path: JavaSource/org/owasp/webgoat/lessons/Encoding.java, line 640
Info: The MD5 hash (used in java.security.MessageDigest.getInstance) is insecure. Consider changing it to a secure hash algorithm
✗ [Low] Sensitive Cookie Without 'HttpOnly' Flag
Path: JavaSource/org/owasp/webgoat/lessons/WeakSessionID.java, line 208
Info: Cookie misses a call to setHttpOnly. Set the HttpOnly flag to true to protect the cookie from possible malicious code on client side.
✗ [Low] Sensitive Cookie Without 'HttpOnly' Flag
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 171
Info: Cookie misses a call to setHttpOnly. Set the HttpOnly flag to true to protect the cookie from possible malicious code on client side.
✗ [Low] Sensitive Cookie Without 'HttpOnly' Flag
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 192
Info: Cookie misses a call to setHttpOnly. Set the HttpOnly flag to true to protect the cookie from possible malicious code on client side.
✗ [Low] Sensitive Cookie Without 'HttpOnly' Flag
Path: JavaSource/org/owasp/webgoat/lessons/WeakAuthenticationCookie.java, line 144
Info: Cookie misses a call to setHttpOnly. Set the HttpOnly flag to true to protect the cookie from possible malicious code on client side.
✗ [Low] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 124
Info: Do not hardcode credentials in code.
✗ [Low] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/WeakAuthenticationCookie.java, line 93
Info: Do not hardcode credentials in code.
✗ [Low] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/WeakAuthenticationCookie.java, line 98
Info: Do not hardcode credentials in code.
✗ [Low] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/WeakAuthenticationCookie.java, line 104
Info: Do not hardcode credentials in code.
✗ [Low] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/WeakAuthenticationCookie.java, line 133
Info: Do not hardcode credentials in code.
✗ [Low] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/WeakAuthenticationCookie.java, line 137
Info: Do not hardcode credentials in code.
✗ [Low] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/WSDLScanning.java, line 146
Info: Do not hardcode credentials in code.
✗ [Low] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/HtmlClues.java, line 83
Info: Do not hardcode credentials in code.
✗ [Medium] Cleartext Transmission of Sensitive Information
Path: JavaSource/org/owasp/webgoat/util/Interceptor.java, line 97
Info: Writing to an unencrypted socket is insecure - a man-in-the-middle attacker can tamper the messages. Consider using SSL sockets.
✗ [Medium] Cleartext Transmission of Sensitive Information
Path: JavaSource/org/owasp/webgoat/util/Interceptor.java, line 98
Info: Reading from an unencrypted socket is insecure - a man-in-the-middle attacker can tamper the messages. Consider using SSL sockets.
✗ [Medium] Improper Neutralization of CRLF Sequences in HTTP Headers
Path: JavaSource/org/owasp/webgoat/lessons/HttpOnly.java, line 195
Info: Unsanitized input from cookies flows into setHeader and reaches an HTTP header returned to the user. This may allow a malicious input that contain CR/LF to split the http response into two responses and the second response to be controlled by the attacker. This may be used to mount a range of attacks such as cross-site scripting or cache poisoning.
✗ [Medium] Improper Neutralization of CRLF Sequences in HTTP Headers
Path: JavaSource/org/owasp/webgoat/lessons/HttpOnly.java, line 198
Info: Unsanitized input from cookies flows into setHeader and reaches an HTTP header returned to the user. This may allow a malicious input that contain CR/LF to split the http response into two responses and the second response to be controlled by the attacker. This may be used to mount a range of attacks such as cross-site scripting or cache poisoning.
✗ [Medium] Improper Neutralization of CRLF Sequences in HTTP Headers
Path: JavaSource/org/owasp/webgoat/lessons/HttpOnly.java, line 209
Info: Unsanitized input from cookies flows into setHeader and reaches an HTTP header returned to the user. This may allow a malicious input that contain CR/LF to split the http response into two responses and the second response to be controlled by the attacker. This may be used to mount a range of attacks such as cross-site scripting or cache poisoning.
✗ [Medium] Improper Neutralization of CRLF Sequences in HTTP Headers
Path: JavaSource/org/owasp/webgoat/lessons/HttpOnly.java, line 212
Info: Unsanitized input from cookies flows into setHeader and reaches an HTTP header returned to the user. This may allow a malicious input that contain CR/LF to split the http response into two responses and the second response to be controlled by the attacker. This may be used to mount a range of attacks such as cross-site scripting or cache poisoning.
✗ [Medium] Improper Neutralization of CRLF Sequences in HTTP Headers
Path: JavaSource/org/owasp/webgoat/session/WebSession.java, line 335
Info: Unsanitized input from cookies flows into addCookie and reaches an HTTP header returned to the user. This may allow a malicious input that contain CR/LF to split the http response into two responses and the second response to be controlled by the attacker. This may be used to mount a range of attacks such as cross-site scripting or cache poisoning.
✗ [Medium] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 153
Info: Do not hardcode passwords in code. Found hardcoded password used in equals.
✗ [Medium] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/lessons/HtmlClues.java, line 83
Info: Do not hardcode passwords in code. Found hardcoded password used in equals.
✗ [Medium] Use of Hardcoded Credentials
Path: JavaSource/org/owasp/webgoat/session/CreateDB.java, line 72
Info: Do not hardcode passwords in code. Found hardcoded password used in here.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 220
Info: Unsanitized input from cookies flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/CrossSiteScripting/UpdateProfile.java, line 248
Info: Unsanitized input from an HTTP parameter flows into executeUpdate, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/CrossSiteScripting/UpdateProfile.java, line 340
Info: Unsanitized input from an HTTP parameter flows into executeUpdate, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/DOS_Login.java, line 134
Info: Unsanitized input from an HTTP parameter flows into executeUpdate, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/RoleBasedAccessControl/UpdateProfile.java, line 295
Info: Unsanitized input from an HTTP parameter flows into executeUpdate, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/BackDoors.java, line 106
Info: Unsanitized input from an HTTP parameter flows into executeUpdate, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/SQLInjection/ViewProfile.java, line 118
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/SQLInjection/ViewProfile.java, line 178
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/SQLInjection/Login.java, line 149
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/SQLInjection/Login.java, line 191
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/SqlNumericInjection.java, line 130
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/DOS_Login.java, line 114
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/RoleBasedAccessControl/Login.java, line 148
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/BlindSqlInjection.java, line 122
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/SqlStringInjection.java, line 112
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/WsSqlInjection.java, line 240
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/admin/ViewDatabase.java, line 89
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/ThreadSafetyProblem.java, line 103
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/RoleBasedAccessControl/UpdateProfile.java, line 176
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] SQL Injection
Path: JavaSource/org/owasp/webgoat/lessons/BackDoors.java, line 113
Info: Unsanitized input from an HTTP parameter flows into executeQuery, where it is used in an SQL query. This may result in an SQL Injection vulnerability.
✗ [High] Path Traversal
Path: JavaSource/org/owasp/webgoat/lessons/admin/SummaryReportCardScreen.java, line 89
Info: Unsanitized input from an HTTP parameter flows into java.io.FileInputStream, where it is used as a path. This may result in a Path Traversal vulnerability and allow an attacker to read arbitrary files.
✗ [High] Path Traversal
Path: JavaSource/org/owasp/webgoat/lessons/admin/ReportCardScreen.java, line 164
Info: Unsanitized input from an HTTP parameter flows into java.io.FileInputStream, where it is used as a path. This may result in a Path Traversal vulnerability and allow an attacker to read arbitrary files.
✗ [High] Path Traversal
Path: JavaSource/org/owasp/webgoat/util/Interceptor.java, line 135
Info: Unsanitized input from the request URL flows into getRequestDispatcher, where it is used as a path. This may result in a Path Traversal vulnerability and allow an attacker to read arbitrary files.
✗ [High] Command Injection
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 649
Info: Unsanitized input from an HTTP parameter flows into exec, where it is used as a shell command. This may result in a Command Injection vulnerability.
✗ [High] Command Injection
Path: JavaSource/org/owasp/webgoat/lessons/Challenge2Screen.java, line 654
Info: Unsanitized input from an HTTP parameter flows into exec, where it is used as a shell command. This may result in a Command Injection vulnerability.
✗ [High] XML External Entity (XXE) Injection
Path: JavaSource/org/owasp/webgoat/lessons/WsSAXInjection.java, line 179
Info: Unsanitized input from an HTTP parameter flows into parse, which allows expansion of external entity references. This may result in a XXE attack leading to the disclosure of confidential data or denial of service.
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/lessons/SQLInjection/SearchStaff.jsp, line 11
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/lessons/CrossSiteScripting/ViewProfile.jsp, line 171
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/lessons/CrossSiteScripting/SearchStaff.jsp, line 11
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/lessons/RoleBasedAccessControl/SearchStaff.jsp, line 11
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/main.jsp, line 114
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/main.jsp, line 119
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/main.jsp, line 124
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/main.jsp, line 130
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/main.jsp, line 135
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/main.jsp, line 163
Info: Unsanitized input from an HTTP parameter flows into print, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] Cross-site Scripting (XSS)
Path: WebContent/main.jsp, line 191
Info: Unsanitized input from cookies flows into println, where it is used to render an HTML page returned to the user. This may result in a Cross-Site Scripting attack (XSS).
✗ [High] XPath Injection
Path: JavaSource/org/owasp/webgoat/lessons/XPATHInjection.java, line 158
Info: Unsanitized input from an HTTP parameter flows into evaluate, where it is used in an XPath query. This may result in an XPath Injection vulnerability.
✗ [High] Hardcoded Secret
Path: JavaSource/org/owasp/webgoat/lessons/Encoding.java, line 487
Info: Hardcoded value array {...} is used as a cipher salt. Generate the value with a cryptographically strong random number generator such as java.security.SecureRandom instead.
✗ [High] Hardcoded Secret
Path: JavaSource/org/owasp/webgoat/lessons/Encoding.java, line 531
Info: Hardcoded value array {...} is used as a cipher salt. Generate the value with a cryptographically strong random number generator such as java.security.SecureRandom instead.
✔ Test completed
Organization: esecuvali-8y3
Test type: Static code analysis
Project path: D:\0_tmp\snyk\webgoat1
Summary:
71 Code issues found
40 [High] 10 [Medium] 21 [Low]
Open Source
Testing D:\0_tmp\eCommerceWebsite...
Tested 31 dependencies for known issues, found 13 issues, 13 vulnerable paths.
Issues to fix by upgrading:
Upgrade com.fasterxml.jackson.core:jackson-databind@2.11.2 to com.fasterxml.jackson.core:jackson-databind@2.12.7.1 to fix
✗ Denial of Service (DoS) [Medium Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-3038424] in com.fasterxml.jackson.core:jackson-databind@2.11.2
introduced by com.fasterxml.jackson.core:jackson-databind@2.11.2
✗ Denial of Service (DoS) [Medium Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-3038426] in com.fasterxml.jackson.core:jackson-databind@2.11.2
introduced by com.fasterxml.jackson.core:jackson-databind@2.11.2
✗ Denial of Service (DoS) [Medium Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-2326698] in com.fasterxml.jackson.core:jackson-databind@2.11.2
introduced by com.fasterxml.jackson.core:jackson-databind@2.11.2
✗ Denial of Service (DoS) [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-2421244] in com.fasterxml.jackson.core:jackson-databind@2.11.2
introduced by com.fasterxml.jackson.core:jackson-databind@2.11.2
Upgrade com.google.code.gson:gson@2.8.6 to com.google.code.gson:gson@2.8.9 to fix
✗ Deserialization of Untrusted Data [Medium Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMGOOGLECODEGSON-1730327] in com.google.code.gson:gson@2.8.6
introduced by com.google.code.gson:gson@2.8.6
Upgrade mysql:mysql-connector-java@5.1.45 to mysql:mysql-connector-java@8.0.28 to fix
✗ Improper Authorization [Medium Severity][https://security.snyk.io/vuln/SNYK-JAVA-MYSQL-2386864] in mysql:mysql-connector-java@5.1.45
introduced by mysql:mysql-connector-java@5.1.45
✗ XML External Entity (XXE) Injection [Medium Severity][https://security.snyk.io/vuln/SNYK-JAVA-MYSQL-1766958] in mysql:mysql-connector-java@5.1.45
introduced by mysql:mysql-connector-java@5.1.45
✗ Privilege Escalation [Medium Severity][https://security.snyk.io/vuln/SNYK-JAVA-MYSQL-174574] in mysql:mysql-connector-java@5.1.45
introduced by mysql:mysql-connector-java@5.1.45
✗ Access Control Bypass [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-MYSQL-451464] in mysql:mysql-connector-java@5.1.45
introduced by mysql:mysql-connector-java@5.1.45
Upgrade org.hibernate:hibernate-core@5.4.10.Final to org.hibernate:hibernate-core@5.4.24.Final to fix
✗ SQL Injection [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-ORGHIBERNATE-1041788] in org.hibernate:hibernate-core@5.4.10.Final
introduced by org.hibernate:hibernate-core@5.4.10.Final
✗ SQL Injection [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-ORGHIBERNATE-584563] in org.hibernate:hibernate-core@5.4.10.Final
introduced by org.hibernate:hibernate-core@5.4.10.Final
✗ XML External Entity (XXE) Injection [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-ORGDOM4J-565810] in org.dom4j:dom4j@2.1.1
introduced by org.hibernate:hibernate-core@5.4.10.Final > org.dom4j:dom4j@2.1.1
Issues with no direct upgrade or patch:
✗ XML External Entity (XXE) Injection [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-JSTL-30453] in jstl:jstl@1.2
introduced by jstl:jstl@1.2
No upgrade or patch available
Organization: esecuvali-8y3
Package manager: maven
Target file: pom.xml
Project name: com.team.hknp:eCommerceWebsite
Open source: no
Project path: D:\0_tmp\eCommerceWebsite
Licenses: enabled