{"api_version":"1","generated_at":"2026-07-23T13:42:14+00:00","cve":"CVE-2018-1000531","urls":{"html":"https://cve.report/CVE-2018-1000531","api":"https://cve.report/api/cve/CVE-2018-1000531.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2018-1000531","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2018-1000531"},"summary":{"title":"CVE-2018-1000531","description":"inversoft prime-jwt version prior to commit abb0d479389a2509f939452a6767dc424bb5e6ba contains a CWE-20 vulnerability in JWTDecoder.decode that can result in an incorrect signature validation of a JWT token. This attack can be exploitable when an attacker crafts a JWT token with a valid header using 'none' as algorithm and a body to requests it be validated. This vulnerability was fixed after commit abb0d479389a2509f939452a6767dc424bb5e6ba.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2018-06-26 16:29:00","updated_at":"2018-08-30 19:23:00"},"problem_types":["CWE-20"],"metrics":[],"references":[{"url":"https://github.com/inversoft/prime-jwt/issues/3","name":"https://github.com/inversoft/prime-jwt/issues/3","refsource":"MISC","tags":["Third Party Advisory"],"title":"JWT signature validation can be bypassed in versions <= 1.3.0  · Issue #3 · FusionAuth/fusionauth-jwt · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1000531","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1000531","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2018","cve_id":"1000531","vulnerable":"1","versionEndIncluding":"1.3.0","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"inversoft","cpe5":"prime-jwt","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","DATE_ASSIGNED":"2018-06-23T11:22:33.043401","DATE_REQUESTED":"2018-05-02T17:09:44","ID":"CVE-2018-1000531","REQUESTER":"ricardobgoncales@gmail.com","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":"inversoft prime-jwt version prior to commit abb0d479389a2509f939452a6767dc424bb5e6ba contains a CWE-20 vulnerability in JWTDecoder.decode that can result in an incorrect signature validation of a JWT token. This attack can be exploitable when an attacker crafts a JWT token with a valid header using 'none' as algorithm and a body to requests it be validated. This vulnerability was fixed after commit abb0d479389a2509f939452a6767dc424bb5e6ba."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"name":"https://github.com/inversoft/prime-jwt/issues/3","refsource":"MISC","url":"https://github.com/inversoft/prime-jwt/issues/3"}]}},"nvd":{"publishedDate":"2018-06-26 16:29:00","lastModifiedDate":"2018-08-30 19:23:00","problem_types":["CWE-20"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"NONE","baseScore":7.5,"baseSeverity":"HIGH"},"exploitabilityScore":3.9,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:N/I:P/A:N","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"NONE","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":5},"severity":"MEDIUM","exploitabilityScore":10,"impactScore":2.9,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:inversoft:prime-jwt:*:*:*:*:*:*:*:*","versionEndIncluding":"1.3.0","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2018","CveId":"1000531","Ordinal":"129250","Title":"CVE-2018-1000531","CVE":"CVE-2018-1000531","Year":"2018"},"notes":[{"CveYear":"2018","CveId":"1000531","Ordinal":"1","NoteData":"inversoft prime-jwt version prior to commit abb0d479389a2509f939452a6767dc424bb5e6ba contains a CWE-20 vulnerability in JWTDecoder.decode that can result in an incorrect signature validation of a JWT token. This attack can be exploitable when an attacker crafts a JWT token with a valid header using 'none' as algorithm and a body to requests it be validated. This vulnerability was fixed after commit abb0d479389a2509f939452a6767dc424bb5e6ba.","Type":"Description","Title":null},{"CveYear":"2018","CveId":"1000531","Ordinal":"2","NoteData":"2018-06-26","Type":"Other","Title":"Published"},{"CveYear":"2018","CveId":"1000531","Ordinal":"3","NoteData":"2018-06-27","Type":"Other","Title":"Modified"}]}}}