LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36255: An issue was discovered in IdentityModel (aka ScottBrady.IdentityModel) before 1.3.0.

An issue was discovered in IdentityModel (aka ScottBrady.IdentityModel) before 1.3.0. The Branca implementation allows an attacker to modify and forge authentication tokens.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects ScottBrady.IdentityModel before 1.3.0 when its Branca token implementation is used. The CVE says attackers may modify and forge authentication tokens, which can undermine trust decisions. That is potentially serious for applications using those tokens for login or authorization, but the source bundle provides no CVSS score or confirmed exploitation.

Executive priority

Prioritize this for applications where IdentityModel Branca tokens protect user sessions, admin access, or customer data. If the library is absent or Branca is unused, urgency is lower. Because source detail is sparse, treat inventory confirmation as the first decision point.

Technical view

CVE-2020-36255 is a token integrity issue in the Branca implementation of IdentityModel before 1.3.0. The reported impact is modification and forgery of authentication tokens. The provided sources identify the affected version boundary but do not provide CWE, CVSS, detailed root cause, exploit status, or complete remediation notes beyond the 1.3.0 comparison.

Likely exposure

Exposure is likely limited to applications that depend on ScottBrady.IdentityModel before 1.3.0 and use its Branca implementation for authentication tokens. The source bundle does not identify broader platform, framework, or operating-system exposure.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The business risk comes from possible authentication token forgery if an exposed application relies on the vulnerable Branca implementation.

Researcher notes

The available record is thin: no CVSS, CWE, proof-of-concept status, or detailed fix narrative is provided. The strongest source-grounded facts are the product name, version boundary before 1.3.0, Branca component, and token modification or forgery impact.

Mitigation direction

  • Upgrade ScottBrady.IdentityModel to 1.3.0 or later where Branca tokens are used.
  • Review the linked maintainer issues and 1.3.0 comparison for vendor context.
  • Check vendor guidance for additional workarounds; none are specified in the CVE bundle.
  • Assess whether affected authentication tokens need revocation under your incident policy.

Validation and detection

  • Search dependency manifests and lockfiles for ScottBrady.IdentityModel versions before 1.3.0.
  • Confirm whether the application actually uses the Branca implementation for authentication tokens.
  • Verify deployed artifacts run the remediated library version after upgrade.
  • Review authentication and session logs for unusual token acceptance patterns.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-36255 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.