update samples to work with fast-xml-parser parsing changes around qu…

…otes

Signed-off-by: Amndeep Singh Mann <[email protected]>

test/sample_data/burpsuite/burpsuite-hdf-withraw.json

@@ -1,9 +1,9 @@
 {
   "platform": {
     "name": "Heimdall Tools",
-    "release": "2.6.42"
+    "release": "2.9.4"
   },
-  "version": "2.6.42",
+  "version": "2.9.4",
   "statistics": {},
   "profiles": [
     {
@@ -598,7 +598,7 @@
             }
           ],
           "impact": 0.3,
-          "code": "{\n  \"serialNumber\": \"3606840263549464576\",\n  \"type\": \"16777984\",\n  \"name\": \"Strict transport security not enforced\",\n  \"host\": {\n    \"text\": \"https://zero.webappsecurity.com\",\n    \"ip\": \"54.82.22.214\"\n  },\n  \"path\": \"/\",\n  \"location\": \"/\",\n  \"severity\": \"Low\",\n  \"confidence\": \"Certain\",\n  \"issueBackground\": \"<p> The application fails to prevent users from connecting  to it over unencrypted connections.  An attacker able to modify a legitimate user's network traffic could bypass the application's use of SSL/TLS encryption, and use the application as a platform for attacks against its users. This attack is performed by rewriting HTTPS links as HTTP, so that if a targeted user follows a link to the site from an HTTP page, their browser never attempts to use an encrypted connection. The sslstrip tool  automates this process. </p>\\n<p>\\nTo exploit this vulnerability, an attacker must be suitably positioned to intercept and modify the victim's network traffic.This scenario typically occurs when a client communicates with the server over an insecure connection such as public Wi-Fi, or a corporate or home network that is shared with a compromised computer. Common defenses such as switched networks are not sufficient to prevent this. An attacker situated in the user's ISP or the application's hosting infrastructure could also perform this attack. Note that an advanced adversary could potentially target any connection made over the Internet's core infrastructure. </p>\",\n  \"remediationBackground\": \"<p>The application should instruct web browsers to only access the application using HTTPS. To do this, enable HTTP Strict Transport Security (HSTS) by adding a response header with the name 'Strict-Transport-Security' and the value 'max-age=expireTime', where expireTime is the time in seconds that browsers should remember that the site should only be accessed using HTTPS. Consider adding the 'includeSubDomains' flag if appropriate.</p>\\n<p>Note that because HSTS is a \\\"trust on first use\\\" (TOFU) protocol, a user who has never accessed the application will never have seen the HSTS header, and will therefore still be vulnerable to SSL stripping attacks. To mitigate this risk, you can optionally add the 'preload' flag to the HSTS header, and submit the domain for review by browser vendors.</p>\",\n  \"references\": \"<ul>\\n<li><a href=\\\"https://developer.mozilla.org/en-US/docs/Web/Security/HTTP_strict_transport_security\\\">HTTP Strict Transport Security</a></li>\\n<li><a href=\\\"http://www.thoughtcrime.org/software/sslstrip/\\\">sslstrip</a></li>\\n<li><a href=\\\"https://hstspreload.appspot.com/\\\">HSTS Preload Form</a></li>\\n</ul>\",\n  \"vulnerabilityClassifications\": \"<ul>\\n<li><a href=\\\"https://cwe.mitre.org/data/definitions/523.html\\\">CWE-523: Unprotected Transport of Credentials</a></li>\\n</ul>\"\n}",
+          "code": "{\n  \"serialNumber\": \"3606840263549464576\",\n  \"type\": \"16777984\",\n  \"name\": \"Strict transport security not enforced\",\n  \"host\": {\n    \"text\": \"https://zero.webappsecurity.com\",\n    \"ip\": \"54.82.22.214\"\n  },\n  \"path\": \"/\",\n  \"location\": \"/\",\n  \"severity\": \"Low\",\n  \"confidence\": \"Certain\",\n  \"issueBackground\": \"<p> The application fails to prevent users from connecting  to it over unencrypted connections.  An attacker able to modify a legitimate user's network traffic could bypass the application's use of SSL/TLS encryption, and use the application as a platform for attacks against its users. This attack is performed by rewriting HTTPS links as HTTP, so that if a targeted user follows a link to the site from an HTTP page, their browser never attempts to use an encrypted connection. The sslstrip tool  automates this process. </p>\\n<p>\\nTo exploit this vulnerability, an attacker must be suitably positioned to intercept and modify the victim's network traffic.This scenario typically occurs when a client communicates with the server over an insecure connection such as public Wi-Fi, or a corporate or home network that is shared with a compromised computer. Common defenses such as switched networks are not sufficient to prevent this. An attacker situated in the user's ISP or the application's hosting infrastructure could also perform this attack. Note that an advanced adversary could potentially target any connection made over the Internet's core infrastructure. </p>\",\n  \"remediationBackground\": \"<p>The application should instruct web browsers to only access the application using HTTPS. To do this, enable HTTP Strict Transport Security (HSTS) by adding a response header with the name 'Strict-Transport-Security' and the value 'max-age=expireTime', where expireTime is the time in seconds that browsers should remember that the site should only be accessed using HTTPS. Consider adding the 'includeSubDomains' flag if appropriate.</p>\\n<p>Note that because HSTS is a &quot;trust on first use&quot; (TOFU) protocol, a user who has never accessed the application will never have seen the HSTS header, and will therefore still be vulnerable to SSL stripping attacks. To mitigate this risk, you can optionally add the 'preload' flag to the HSTS header, and submit the domain for review by browser vendors.</p>\",\n  \"references\": \"<ul>\\n<li><a href=\\\"https://developer.mozilla.org/en-US/docs/Web/Security/HTTP_strict_transport_security\\\">HTTP Strict Transport Security</a></li>\\n<li><a href=\\\"http://www.thoughtcrime.org/software/sslstrip/\\\">sslstrip</a></li>\\n<li><a href=\\\"https://hstspreload.appspot.com/\\\">HSTS Preload Form</a></li>\\n</ul>\",\n  \"vulnerabilityClassifications\": \"<ul>\\n<li><a href=\\\"https://cwe.mitre.org/data/definitions/523.html\\\">CWE-523: Unprotected Transport of Credentials</a></li>\\n</ul>\"\n}",
           "results": [
             {
               "status": "failed",
@@ -771,7 +771,7 @@
           ]
         }
       ],
-      "sha256": "62b22b19fecc1f1ef5d6647e109353c08a88d19a9289f03e866904e1c436c044"
+      "sha256": "a1cd7af5e46b87a9384c3893c9ffcc4520ae69bf79212548caa7b61a0e18977e"
     }
   ],
   "passthrough": {
@@ -1679,7 +1679,7 @@
             "severity": "Low",
             "confidence": "Certain",
             "issueBackground": "<p> The application fails to prevent users from connecting  to it over unencrypted connections.  An attacker able to modify a legitimate user's network traffic could bypass the application's use of SSL/TLS encryption, and use the application as a platform for attacks against its users. This attack is performed by rewriting HTTPS links as HTTP, so that if a targeted user follows a link to the site from an HTTP page, their browser never attempts to use an encrypted connection. The sslstrip tool  automates this process. </p>\n<p>\nTo exploit this vulnerability, an attacker must be suitably positioned to intercept and modify the victim's network traffic.This scenario typically occurs when a client communicates with the server over an insecure connection such as public Wi-Fi, or a corporate or home network that is shared with a compromised computer. Common defenses such as switched networks are not sufficient to prevent this. An attacker situated in the user's ISP or the application's hosting infrastructure could also perform this attack. Note that an advanced adversary could potentially target any connection made over the Internet's core infrastructure. </p>",
-            "remediationBackground": "<p>The application should instruct web browsers to only access the application using HTTPS. To do this, enable HTTP Strict Transport Security (HSTS) by adding a response header with the name 'Strict-Transport-Security' and the value 'max-age=expireTime', where expireTime is the time in seconds that browsers should remember that the site should only be accessed using HTTPS. Consider adding the 'includeSubDomains' flag if appropriate.</p>\n<p>Note that because HSTS is a \"trust on first use\" (TOFU) protocol, a user who has never accessed the application will never have seen the HSTS header, and will therefore still be vulnerable to SSL stripping attacks. To mitigate this risk, you can optionally add the 'preload' flag to the HSTS header, and submit the domain for review by browser vendors.</p>",
+            "remediationBackground": "<p>The application should instruct web browsers to only access the application using HTTPS. To do this, enable HTTP Strict Transport Security (HSTS) by adding a response header with the name 'Strict-Transport-Security' and the value 'max-age=expireTime', where expireTime is the time in seconds that browsers should remember that the site should only be accessed using HTTPS. Consider adding the 'includeSubDomains' flag if appropriate.</p>\n<p>Note that because HSTS is a &quot;trust on first use&quot; (TOFU) protocol, a user who has never accessed the application will never have seen the HSTS header, and will therefore still be vulnerable to SSL stripping attacks. To mitigate this risk, you can optionally add the 'preload' flag to the HSTS header, and submit the domain for review by browser vendors.</p>",
             "references": "<ul>\n<li><a href=\"https://developer.mozilla.org/en-US/docs/Web/Security/HTTP_strict_transport_security\">HTTP Strict Transport Security</a></li>\n<li><a href=\"http://www.thoughtcrime.org/software/sslstrip/\">sslstrip</a></li>\n<li><a href=\"https://hstspreload.appspot.com/\">HSTS Preload Form</a></li>\n</ul>",
             "vulnerabilityClassifications": "<ul>\n<li><a href=\"https://cwe.mitre.org/data/definitions/523.html\">CWE-523: Unprotected Transport of Credentials</a></li>\n</ul>"
           },
@@ -1716,7 +1716,7 @@
             "severity": "Low",
             "confidence": "Certain",
             "issueBackground": "<p> The application fails to prevent users from connecting  to it over unencrypted connections.  An attacker able to modify a legitimate user's network traffic could bypass the application's use of SSL/TLS encryption, and use the application as a platform for attacks against its users. This attack is performed by rewriting HTTPS links as HTTP, so that if a targeted user follows a link to the site from an HTTP page, their browser never attempts to use an encrypted connection. The sslstrip tool  automates this process. </p>\n<p>\nTo exploit this vulnerability, an attacker must be suitably positioned to intercept and modify the victim's network traffic.This scenario typically occurs when a client communicates with the server over an insecure connection such as public Wi-Fi, or a corporate or home network that is shared with a compromised computer. Common defenses such as switched networks are not sufficient to prevent this. An attacker situated in the user's ISP or the application's hosting infrastructure could also perform this attack. Note that an advanced adversary could potentially target any connection made over the Internet's core infrastructure. </p>",
-            "remediationBackground": "<p>The application should instruct web browsers to only access the application using HTTPS. To do this, enable HTTP Strict Transport Security (HSTS) by adding a response header with the name 'Strict-Transport-Security' and the value 'max-age=expireTime', where expireTime is the time in seconds that browsers should remember that the site should only be accessed using HTTPS. Consider adding the 'includeSubDomains' flag if appropriate.</p>\n<p>Note that because HSTS is a \"trust on first use\" (TOFU) protocol, a user who has never accessed the application will never have seen the HSTS header, and will therefore still be vulnerable to SSL stripping attacks. To mitigate this risk, you can optionally add the 'preload' flag to the HSTS header, and submit the domain for review by browser vendors.</p>",
+            "remediationBackground": "<p>The application should instruct web browsers to only access the application using HTTPS. To do this, enable HTTP Strict Transport Security (HSTS) by adding a response header with the name 'Strict-Transport-Security' and the value 'max-age=expireTime', where expireTime is the time in seconds that browsers should remember that the site should only be accessed using HTTPS. Consider adding the 'includeSubDomains' flag if appropriate.</p>\n<p>Note that because HSTS is a &quot;trust on first use&quot; (TOFU) protocol, a user who has never accessed the application will never have seen the HSTS header, and will therefore still be vulnerable to SSL stripping attacks. To mitigate this risk, you can optionally add the 'preload' flag to the HSTS header, and submit the domain for review by browser vendors.</p>",
             "references": "<ul>\n<li><a href=\"https://developer.mozilla.org/en-US/docs/Web/Security/HTTP_strict_transport_security\">HTTP Strict Transport Security</a></li>\n<li><a href=\"http://www.thoughtcrime.org/software/sslstrip/\">sslstrip</a></li>\n<li><a href=\"https://hstspreload.appspot.com/\">HSTS Preload Form</a></li>\n</ul>",
             "vulnerabilityClassifications": "<ul>\n<li><a href=\"https://cwe.mitre.org/data/definitions/523.html\">CWE-523: Unprotected Transport of Credentials</a></li>\n</ul>"
           },

test/sample_data/burpsuite/burpsuite-hdf.json

@@ -1,9 +1,9 @@
 {
   "platform": {
     "name": "Heimdall Tools",
-    "release": "2.6.42"
+    "release": "2.9.4"
   },
-  "version": "2.6.42",
+  "version": "2.9.4",
   "statistics": {},
   "profiles": [
     {
@@ -598,7 +598,7 @@
             }
           ],
           "impact": 0.3,
-          "code": "{\n  \"serialNumber\": \"3606840263549464576\",\n  \"type\": \"16777984\",\n  \"name\": \"Strict transport security not enforced\",\n  \"host\": {\n    \"text\": \"https://zero.webappsecurity.com\",\n    \"ip\": \"54.82.22.214\"\n  },\n  \"path\": \"/\",\n  \"location\": \"/\",\n  \"severity\": \"Low\",\n  \"confidence\": \"Certain\",\n  \"issueBackground\": \"<p> The application fails to prevent users from connecting  to it over unencrypted connections.  An attacker able to modify a legitimate user's network traffic could bypass the application's use of SSL/TLS encryption, and use the application as a platform for attacks against its users. This attack is performed by rewriting HTTPS links as HTTP, so that if a targeted user follows a link to the site from an HTTP page, their browser never attempts to use an encrypted connection. The sslstrip tool  automates this process. </p>\\n<p>\\nTo exploit this vulnerability, an attacker must be suitably positioned to intercept and modify the victim's network traffic.This scenario typically occurs when a client communicates with the server over an insecure connection such as public Wi-Fi, or a corporate or home network that is shared with a compromised computer. Common defenses such as switched networks are not sufficient to prevent this. An attacker situated in the user's ISP or the application's hosting infrastructure could also perform this attack. Note that an advanced adversary could potentially target any connection made over the Internet's core infrastructure. </p>\",\n  \"remediationBackground\": \"<p>The application should instruct web browsers to only access the application using HTTPS. To do this, enable HTTP Strict Transport Security (HSTS) by adding a response header with the name 'Strict-Transport-Security' and the value 'max-age=expireTime', where expireTime is the time in seconds that browsers should remember that the site should only be accessed using HTTPS. Consider adding the 'includeSubDomains' flag if appropriate.</p>\\n<p>Note that because HSTS is a \\\"trust on first use\\\" (TOFU) protocol, a user who has never accessed the application will never have seen the HSTS header, and will therefore still be vulnerable to SSL stripping attacks. To mitigate this risk, you can optionally add the 'preload' flag to the HSTS header, and submit the domain for review by browser vendors.</p>\",\n  \"references\": \"<ul>\\n<li><a href=\\\"https://developer.mozilla.org/en-US/docs/Web/Security/HTTP_strict_transport_security\\\">HTTP Strict Transport Security</a></li>\\n<li><a href=\\\"http://www.thoughtcrime.org/software/sslstrip/\\\">sslstrip</a></li>\\n<li><a href=\\\"https://hstspreload.appspot.com/\\\">HSTS Preload Form</a></li>\\n</ul>\",\n  \"vulnerabilityClassifications\": \"<ul>\\n<li><a href=\\\"https://cwe.mitre.org/data/definitions/523.html\\\">CWE-523: Unprotected Transport of Credentials</a></li>\\n</ul>\"\n}",
+          "code": "{\n  \"serialNumber\": \"3606840263549464576\",\n  \"type\": \"16777984\",\n  \"name\": \"Strict transport security not enforced\",\n  \"host\": {\n    \"text\": \"https://zero.webappsecurity.com\",\n    \"ip\": \"54.82.22.214\"\n  },\n  \"path\": \"/\",\n  \"location\": \"/\",\n  \"severity\": \"Low\",\n  \"confidence\": \"Certain\",\n  \"issueBackground\": \"<p> The application fails to prevent users from connecting  to it over unencrypted connections.  An attacker able to modify a legitimate user's network traffic could bypass the application's use of SSL/TLS encryption, and use the application as a platform for attacks against its users. This attack is performed by rewriting HTTPS links as HTTP, so that if a targeted user follows a link to the site from an HTTP page, their browser never attempts to use an encrypted connection. The sslstrip tool  automates this process. </p>\\n<p>\\nTo exploit this vulnerability, an attacker must be suitably positioned to intercept and modify the victim's network traffic.This scenario typically occurs when a client communicates with the server over an insecure connection such as public Wi-Fi, or a corporate or home network that is shared with a compromised computer. Common defenses such as switched networks are not sufficient to prevent this. An attacker situated in the user's ISP or the application's hosting infrastructure could also perform this attack. Note that an advanced adversary could potentially target any connection made over the Internet's core infrastructure. </p>\",\n  \"remediationBackground\": \"<p>The application should instruct web browsers to only access the application using HTTPS. To do this, enable HTTP Strict Transport Security (HSTS) by adding a response header with the name 'Strict-Transport-Security' and the value 'max-age=expireTime', where expireTime is the time in seconds that browsers should remember that the site should only be accessed using HTTPS. Consider adding the 'includeSubDomains' flag if appropriate.</p>\\n<p>Note that because HSTS is a &quot;trust on first use&quot; (TOFU) protocol, a user who has never accessed the application will never have seen the HSTS header, and will therefore still be vulnerable to SSL stripping attacks. To mitigate this risk, you can optionally add the 'preload' flag to the HSTS header, and submit the domain for review by browser vendors.</p>\",\n  \"references\": \"<ul>\\n<li><a href=\\\"https://developer.mozilla.org/en-US/docs/Web/Security/HTTP_strict_transport_security\\\">HTTP Strict Transport Security</a></li>\\n<li><a href=\\\"http://www.thoughtcrime.org/software/sslstrip/\\\">sslstrip</a></li>\\n<li><a href=\\\"https://hstspreload.appspot.com/\\\">HSTS Preload Form</a></li>\\n</ul>\",\n  \"vulnerabilityClassifications\": \"<ul>\\n<li><a href=\\\"https://cwe.mitre.org/data/definitions/523.html\\\">CWE-523: Unprotected Transport of Credentials</a></li>\\n</ul>\"\n}",
           "results": [
             {
               "status": "failed",
@@ -771,7 +771,7 @@
           ]
         }
       ],
-      "sha256": "62b22b19fecc1f1ef5d6647e109353c08a88d19a9289f03e866904e1c436c044"
+      "sha256": "a1cd7af5e46b87a9384c3893c9ffcc4520ae69bf79212548caa7b61a0e18977e"
     }
   ],
   "passthrough": {}