CVE-2014-6393 (GCVE-0-2014-6393)

Vulnerability from cvelistv5 – Published: 2017-08-09 18:00 – Updated: 2024-08-06 12:17
VLAI?
Summary
The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding.
Severity ?
No CVSS data available.
CWE
  • n/a
Assigner
References
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-06T12:17:23.956Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://nodesecurity.io/advisories/express-no-charset-in-content-type-header"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1203190"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "datePublic": "2014-09-12T00:00:00",
      "descriptions": [
        {
          "lang": "en",
          "value": "The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-08-09T17:57:01",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://nodesecurity.io/advisories/express-no-charset-in-content-type-header"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1203190"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2014-6393",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://nodesecurity.io/advisories/express-no-charset-in-content-type-header",
              "refsource": "CONFIRM",
              "url": "https://nodesecurity.io/advisories/express-no-charset-in-content-type-header"
            },
            {
              "name": "https://bugzilla.redhat.com/show_bug.cgi?id=1203190",
              "refsource": "CONFIRM",
              "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1203190"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2014-6393",
    "datePublished": "2017-08-09T18:00:00",
    "dateReserved": "2014-09-15T00:00:00",
    "dateUpdated": "2024-08-06T12:17:23.956Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:*:*:*:*:*:*:*:*\", \"versionEndIncluding\": \"3.10.5\", \"matchCriteriaId\": \"F3044B30-C7BD-4472-B79F-1B1CF6678B83\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.0.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"7048C98D-3862-4067-BBD9-FED2488EAAA9\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.1.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"41978223-8371-41B6-A5AA-C270357ECE88\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.1.1:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"1DC94FA3-2F6E-4C11-AFF9-EBE99661E3CE\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.1.2:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"E3EE054C-7B48-46FC-B048-458A138718A5\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.2.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"5CAF101E-20FC-40EC-9566-6274E24D668D\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.3.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"1E93C3DE-988C-47D9-84BB-0579D83A05C8\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.3.1:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"E80EDF16-E5CF-4B61-B041-54D2D33B2A13\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.3.2:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"89706C45-EE55-4778-AE2A-53DCFFEC45D4\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.4.0:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"C29C2745-5E28-42EE-AA8D-5EAB394AC813\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.4.1:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"13FFEADC-67C9-4270-B832-696BF41ADE2F\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.4.2:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"7F8DC1AA-D87C-4DC6-9735-56A78719E96A\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.4.3:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"2B020CA0-739E-4404-A1D1-59B826F3DC3D\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.4.4:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"080B58C4-1910-43C5-AAF6-2134416E9685\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:a:openjsf:express:4.4.5:*:*:*:*:*:*:*\", \"matchCriteriaId\": \"F71DFB79-FD8C-4470-8B3B-8FA1E4FE2F41\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding.\"}, {\"lang\": \"es\", \"value\": \"El framework web Express en versiones anteriores a la 3.11 y en versiones 4.x anteriores a la 4.5 para Node.js no proporciona un campo charset en los encabezados HTTP Content-Type en respuestas de nivel 400. Esto permitir\\u00eda que atacantes remotos llevasen a cabo ataques de tipo cross-site scripting (XSS) mediante caracteres en una codificaci\\u00f3n no est\\u00e1ndar.\"}]",
      "id": "CVE-2014-6393",
      "lastModified": "2024-11-21T02:14:18.290",
      "metrics": "{\"cvssMetricV30\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.0\", \"vectorString\": \"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\", \"baseScore\": 6.1, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"NONE\", \"userInteraction\": \"REQUIRED\", \"scope\": \"CHANGED\", \"confidentialityImpact\": \"LOW\", \"integrityImpact\": \"LOW\", \"availabilityImpact\": \"NONE\"}, \"exploitabilityScore\": 2.8, \"impactScore\": 2.7}], \"cvssMetricV2\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"2.0\", \"vectorString\": \"AV:N/AC:M/Au:N/C:N/I:P/A:N\", \"baseScore\": 4.3, \"accessVector\": \"NETWORK\", \"accessComplexity\": \"MEDIUM\", \"authentication\": \"NONE\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"PARTIAL\", \"availabilityImpact\": \"NONE\"}, \"baseSeverity\": \"MEDIUM\", \"exploitabilityScore\": 8.6, \"impactScore\": 2.9, \"acInsufInfo\": false, \"obtainAllPrivilege\": false, \"obtainUserPrivilege\": false, \"obtainOtherPrivilege\": false, \"userInteractionRequired\": true}]}",
      "published": "2017-08-09T18:29:00.480",
      "references": "[{\"url\": \"https://bugzilla.redhat.com/show_bug.cgi?id=1203190\", \"source\": \"cve@mitre.org\", \"tags\": [\"Issue Tracking\", \"Third Party Advisory\", \"VDB Entry\"]}, {\"url\": \"https://nodesecurity.io/advisories/express-no-charset-in-content-type-header\", \"source\": \"cve@mitre.org\", \"tags\": [\"Third Party Advisory\"]}, {\"url\": \"https://bugzilla.redhat.com/show_bug.cgi?id=1203190\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Issue Tracking\", \"Third Party Advisory\", \"VDB Entry\"]}, {\"url\": \"https://nodesecurity.io/advisories/express-no-charset-in-content-type-header\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Third Party Advisory\"]}]",
      "sourceIdentifier": "cve@mitre.org",
      "vulnStatus": "Modified",
      "weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-79\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2014-6393\",\"sourceIdentifier\":\"cve@mitre.org\",\"published\":\"2017-08-09T18:29:00.480\",\"lastModified\":\"2025-04-20T01:37:25.860\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding.\"},{\"lang\":\"es\",\"value\":\"El framework web Express en versiones anteriores a la 3.11 y en versiones 4.x anteriores a la 4.5 para Node.js no proporciona un campo charset en los encabezados HTTP Content-Type en respuestas de nivel 400. Esto permitir\u00eda que atacantes remotos llevasen a cabo ataques de tipo cross-site scripting (XSS) mediante caracteres en una codificaci\u00f3n no est\u00e1ndar.\"}],\"metrics\":{\"cvssMetricV30\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.0\",\"vectorString\":\"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N\",\"baseScore\":6.1,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"REQUIRED\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.8,\"impactScore\":2.7}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:M/Au:N/C:N/I:P/A:N\",\"baseScore\":4.3,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"MEDIUM\",\"authentication\":\"NONE\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"PARTIAL\",\"availabilityImpact\":\"NONE\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":8.6,\"impactScore\":2.9,\"acInsufInfo\":false,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":true}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-79\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:*:*:*:*:*:*:*:*\",\"versionEndIncluding\":\"3.10.5\",\"matchCriteriaId\":\"F3044B30-C7BD-4472-B79F-1B1CF6678B83\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.0.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"7048C98D-3862-4067-BBD9-FED2488EAAA9\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.1.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"41978223-8371-41B6-A5AA-C270357ECE88\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.1.1:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"1DC94FA3-2F6E-4C11-AFF9-EBE99661E3CE\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.1.2:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"E3EE054C-7B48-46FC-B048-458A138718A5\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.2.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"5CAF101E-20FC-40EC-9566-6274E24D668D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.3.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"1E93C3DE-988C-47D9-84BB-0579D83A05C8\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.3.1:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"E80EDF16-E5CF-4B61-B041-54D2D33B2A13\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.3.2:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"89706C45-EE55-4778-AE2A-53DCFFEC45D4\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.4.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"C29C2745-5E28-42EE-AA8D-5EAB394AC813\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.4.1:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"13FFEADC-67C9-4270-B832-696BF41ADE2F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.4.2:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"7F8DC1AA-D87C-4DC6-9735-56A78719E96A\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.4.3:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"2B020CA0-739E-4404-A1D1-59B826F3DC3D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.4.4:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"080B58C4-1910-43C5-AAF6-2134416E9685\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:openjsf:express:4.4.5:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"F71DFB79-FD8C-4470-8B3B-8FA1E4FE2F41\"}]}]}],\"references\":[{\"url\":\"https://bugzilla.redhat.com/show_bug.cgi?id=1203190\",\"source\":\"cve@mitre.org\",\"tags\":[\"Issue Tracking\",\"Third Party Advisory\",\"VDB Entry\"]},{\"url\":\"https://nodesecurity.io/advisories/express-no-charset-in-content-type-header\",\"source\":\"cve@mitre.org\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://bugzilla.redhat.com/show_bug.cgi?id=1203190\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Issue Tracking\",\"Third Party Advisory\",\"VDB Entry\"]},{\"url\":\"https://nodesecurity.io/advisories/express-no-charset-in-content-type-header\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Third Party Advisory\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.