Skip to content

Commit

Permalink
Remove malicious-looking stuff from CVE-1969-12345
Browse files Browse the repository at this point in the history
  • Loading branch information
todb authored Jul 6, 2023
1 parent 34b083e commit 393b6a4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions CVE-1969-12345.json
Original file line number Diff line number Diff line change
Expand Up @@ -45,10 +45,10 @@
{
"base64": false,
"type": "text/html",
"value": "This CVE is a reference entry design to test various aspects of downstream parsers. It contains some, but not all, required and optional fields. It is similar in function to other valid, properly formatted components of other systems, such as <a target=\"_blank\" rel=\"nofollow\" href=\"https://example.com\">https://example.com</a>, [email protected], &lt;script&gt;alert(1)&lt;/script&gt;, the adventures of Alice and Bob, and the EICAR test file:<br><br>X5O!P%@AP[4\\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*<br><br>CVE entry parsers should not interpret any of this description as either malicious or executable, of course, nor should they automatically download and parse reference links, as they may, in fact, contain malicious code, outside of the control of the CVE Project.<br><br>This entry may be updated from time to time in response to user requests, but it should always be a validly formatted CVE entry, and some optional fields should be left intentionally blank.<br><br>"
"value": "This CVE is a reference entry design to test the retrieval and basic parsing of a CVE entry. It contains some, but not all, required and optional fields.<br><br>This entry may be updated from time to time in response to user requests, but it should always be a validly formatted CVE entry, and some optional fields should be left intentionally blank.<br><br>"
}
],
"value": "This CVE is a reference entry design to test various aspects of downstream parsers. It contains some, but not all, required and optional fields. It is similar in function to other valid, properly formatted components of other systems, such as https://example.com https://example.com , [email protected], <script>alert(1)</script>, the adventures of Alice and Bob, and the EICAR test file:\n\nX5O!P%@AP[4\\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*\n\nCVE entry parsers should not interpret any of this description as either malicious or executable, of course, nor should they automatically download and parse reference links, as they may, in fact, contain malicious code, outside of the control of the CVE Project.\n\nThis entry may be updated from time to time in response to user requests, but it should always be a validly formatted CVE entry, and some optional fields should be left intentionally blank.\n\n"
"value": "This CVE is a reference entry design to test the retrieval and basic parsing of a CVE entry. It contains some, but not all, required and optional fields.\n\nThis entry may be updated from time to time in response to user requests, but it should always be a validly formatted CVE entry, and some optional fields should be left intentionally blank.\n\n"
}
],
"impacts": [
Expand Down

0 comments on commit 393b6a4

Please sign in to comment.