node/test/fixtures/x509-escaping/package.json

{
  "name": "x509-escaping",
  "version": "1.0.0",
  "description": "create certificates for x509-escaping test",
  "main": "createCert.js",
  "license": "SEE LICENSE IN ../../../LICENSE",
  "private": true,
  "dependencies": {
    "asn1.js": "^5.4.1",
    "asn1.js-rfc5280": "^3.0.0"
  }
}
crypto,tls: implement safe x509 GeneralName format This change introduces JSON-compatible escaping rules for strings that include X.509 GeneralName components (see RFC 5280). This non-standard format avoids ambiguities and prevents injection attacks that could previously lead to X.509 certificates being accepted even though they were not valid for the target hostname. These changes affect the format of subject alternative names and the format of authority information access. The checkServerIdentity function has been modified to safely handle the new format, eliminating the possibility of injecting subject alternative names into the verification logic. Because each subject alternative name is only encoded as a JSON string literal if necessary for security purposes, this change will only be visible in rare cases. This addresses CVE-2021-44532. CVE-ID: CVE-2021-44532 PR-URL: https://github.com/nodejs-private/node-private/pull/300 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Rich Trott <rtrott@gmail.com> 2021-12-07 00:21:28 +00:00			`{`
			`"name": "x509-escaping",`
			`"version": "1.0.0",`
			`"description": "create certificates for x509-escaping test",`
			`"main": "createCert.js",`
			`"license": "SEE LICENSE IN ../../../LICENSE",`
			`"private": true,`
			`"dependencies": {`
			`"asn1.js": "^5.4.1",`
			`"asn1.js-rfc5280": "^3.0.0"`
			`}`
			`}`