An attacker obtains an authoritative or reputable signer's private signature key by exploiting a cryptographic weakness in the signature algorithm or pseudorandom number generation and then uses this key to forge signatures from the original signer to mislead a victim into performing actions that benefit the attacker.
Likelihood Of Attack
Low
Typical Severity
High
Relationships
This table shows the other attack patterns and high level categories that are related to this attack pattern. These relationships are defined as ChildOf and ParentOf, and give insight to similar items that may exist at higher and lower levels of abstraction. In addition, relationships such as CanFollow, PeerOf, and CanAlsoBe are defined to show similar attack patterns that the user may want to explore.
Nature
Type
ID
Name
ChildOf
Standard Attack Pattern - A standard level attack pattern in CAPEC is focused on a specific methodology or technique used in an attack. It is often seen as a singular piece of a fully executed attack. A standard attack pattern is meant to provide sufficient details to understand the specific technique and how it attempts to accomplish a desired goal. A standard level attack pattern is a specific type of a more abstract meta level attack pattern.
An authoritative signer is using a weak method of random number generation or weak signing software that causes key leakage or permits key inference.
An authoritative signer is using a signature algorithm with a direct weakness or with poorly chosen parameters that enable the key to be recovered using signatures from that signer.
Skills Required
[Level: High]
Cryptanalysis of signature generation algorithm
[Level: High]
Reverse engineering and cryptanalysis of signature generation algorithm implementation and random number generation
[Level: High]
Ability to create malformed data blobs and know how to present them directly or indirectly to a victim.
Mitigations
Ensure cryptographic elements have been sufficiently tested for weaknesses.
Related Weaknesses
A Related Weakness relationship associates a weakness with this attack pattern. Each association implies a weakness that must exist for a given attack to be successful. If multiple weaknesses are associated with the attack pattern, then any of the weaknesses (but not necessarily all) may be present for the attack to be successful. Each related weakness is identified by a CWE identifier.
CAPEC mappings to ATT&CK techniques leverage an inheritance model to streamline and minimize direct CAPEC/ATT&CK mappings. Inheritance of a mapping is indicated by text stating that the parent CAPEC has relevant ATT&CK mappings. Note that the ATT&CK Enterprise Framework does not use an inheritance model as part of the mapping to CAPEC.
Relevant to the ATT&CK taxonomy mapping (also see parent)
[REF-419] P.J. Leadbitter, D. Page
and N.P. Smart. "Attacking DSA Under a Repeated Bits Assumption". http://www.iacr.org/archive/ches2004/31560428/31560428.pdf. 2004-07.
[REF-420] Debian Security. "DSA-1571-1 openssl -- predictable random number generator". http://www.debian.org/security/2008/dsa-1571. 2008-05-13.
Content History
Submissions
Submission Date
Submitter
Organization
2014-06-23
(Version 2.6)
CAPEC Content Team
The MITRE Corporation
Modifications
Modification Date
Modifier
Organization
2021-06-24
(Version 3.5)
CAPEC Content Team
The MITRE Corporation
Updated Related_Weaknesses
2022-09-29
(Version 3.8)
CAPEC Content Team
The MITRE Corporation
Updated Taxonomy_Mappings
More information is available — Please select a different filter.
Description
This table shows the other attack patterns and high level categories that are related to this attack pattern. These relationships are defined as ChildOf and ParentOf, and give insight to similar items that may exist at higher and lower levels of abstraction. In addition, relationships such as CanFollow, PeerOf, and CanAlsoBe are defined to show similar attack patterns that the user may want to explore.
Content History
