Security Resilience

CWE · MITRE source

CWE-1270Generation of Incorrect Security Tokens

Abstraction: Base · CVEs in our corpus: 10

The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.

Systems-On-a-Chip (SoC) (Integrated circuits and hardware engines) implement Security Tokens to differentiate and identify actions originated from various agents. These actions could be "read", "write", "program", "reset", "fetch", "compute", etc. Security Tokens are generated and assigned to every agent on the SoC that is either capable of generating an action or receiving an action from another agent. Every agent could be assigned a unique, Security Token based on its trust level or privileges.

Last updated: 15 October 2026 14:21 UTC

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.AA-04
  • PR.PS-06
  • AC-16 Security and Privacy Attributes
  • SA-11 Developer Testing and Evaluation
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2022-31122 7.49.80.00722022-10-18
CVE-2023-2882 7.49.80.00642023-05-25
CVE-2026-49499 6.58.80.00422026-07-22
CVE-2026-545936.28.10.00682026-07-28
CVE-2025-59698 5.16.80.00332025-12-02
CVE-2023-22644 4.45.50.00462023-09-20
CVE-2026-196364.15.30.00262026-08-14
CVE-2023-30524 3.74.30.00432023-04-12
CVE-2026-158313.64.30.00302026-07-29