CVE-2014-1266
published 2014-02-22CVE-2014-1266: The SSLVerifySignedServerKeyExchange function in libsecurity_ssl/lib/sslKeyExchange.c in the Secure Transport feature in the Data Security component in Apple…
PriorityP346high7.4CVSS 3.1
AVNACHPRNUINSUCHIHAN
EPSS
5.71%
92.2th percentile
The SSLVerifySignedServerKeyExchange function in libsecurity_ssl/lib/sslKeyExchange.c in the Secure Transport feature in the Data Security component in Apple iOS 6.x before 6.1.6 and 7.x before 7.0.6, Apple TV 6.x before 6.0.2, and Apple OS X 10.9.x before 10.9.2 does not check the signature in a TLS Server Key Exchange message, which allows man-in-the-middle attackers to spoof SSL servers by (1) using an arbitrary private key for the signing step or (2) omitting the signing step.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apple | iphone_os | >= 6.0 < 6.1.6 | 6.1.6 |
| apple | iphone_os | >= 7.0 < 7.0.6 | 7.0.6 |
| apple | mac_os_x | >= 10.9 < 10.9.2 | 10.9.2 |
| apple | tvos | >= 6.0 < 6.0.2 | 6.0.2 |
CVSS provenance
nvdv3.17.4HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvdv2.05.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:N
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-4j69-27g2-fgcw: The SSLVerifySignedServerKeyExchange function in libsecurity_ssl/lib/sslKeyExchange
ghsa_unreviewed·2022-05-14
CVE-2014-1266 [MEDIUM] CWE-20 GHSA-4j69-27g2-fgcw: The SSLVerifySignedServerKeyExchange function in libsecurity_ssl/lib/sslKeyExchange
The SSLVerifySignedServerKeyExchange function in libsecurity_ssl/lib/sslKeyExchange.c in the Secure Transport feature in the Data Security component in Apple iOS 6.x before 6.1.6 and 7.x before 7.0.6, Apple TV 6.x before 6.0.2, and Apple OS X 10.9.x before 10.9.2 does not check the signature in a TLS Server Key Exchange message, which allows man-in-the-middle attackers to spoof SSL servers by (1) using an arbitrary private key for the signing step or (2) omitting the signing step.
Red Hat
kernel: mptcp: fix UaF in listener shutdown
vendor_redhat·2025-05-02·CVSS 7.8
CVE-2023-53088 [HIGH] kernel: mptcp: fix UaF in listener shutdown
kernel: mptcp: fix UaF in listener shutdown
In the Linux kernel, the following vulnerability has been resolved:
mptcp: fix UaF in listener shutdown
As reported by Christoph after having refactored the passive
socket initialization, the mptcp listener shutdown path is prone
to an UaF issue.
BUG: KASAN: use-after-free in _raw_spin_lock_bh+0x73/0xe0
Write of size 4 at addr ffff88810cb23098 by task syz-executor731/1266
CPU: 1 PID: 1266 Comm: syz-executor731 Not tainted 6.2.0-rc59af4eaa31c1f6c00c8f1e448ed99a45c66340dd5 #6
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014
Call Trace:
dump_stack_lvl+0x6e/0x91
print_report+0x16a/0x46f
kasan_report+0xad/0x130
kasan_check_range+0x14a/0x1a0
_raw_spin_lock_bh+0x73/0xe0
subflow_error_r
No detection rules found.
No public exploits indexed.
CWE
Dead Code
mitre_cwe
CWE-561 Dead Code
CWE-561: Dead Code
The product contains dead code, which can never be executed.
Dead code is code that can never be executed in a running program. The surrounding code makes it impossible for a section of code to ever be executed.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Quality Degradation. Dead code that results from code that can never be executed is an indication of problems with the source code that needs to be fixed and is an indication of poor quality.
Scope: Other. Impact: Reduce Maintainability.
Detection Methods:
Architecture or Design Review: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.
CWE
Channel Accessible by Non-Endpoint
mitre_cwe
CWE-300 Channel Accessible by Non-Endpoint
CWE-300: Channel Accessible by Non-Endpoint
The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint.
In order to establish secure communication between two parties, it is often important to adequately verify the identity of entities at each end of the communication channel. Inadequate or inconsistent verification may result in insufficient or incorrect identification of either communicating entity. This can have negative consequences such as misplaced trust in the entity at the other end of the channel. An attacker can leverage this by interposing between the communicating entities and
CWE
Irrelevant Code
mitre_cwe·CVSS 7.4
[HIGH] CWE-1164 Irrelevant Code
CWE-1164: Irrelevant Code
The product contains code that is not essential for execution,
i.e. makes no state changes and has no side effects that alter
data or control flow, such that removal of the code would have no impact
to functionality or correctness.
Irrelevant code could include dead code,
initialization that is not used, empty blocks, code that could be entirely
removed due to optimization, etc.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Reduce Reliability.
Scope: Other. Impact: Reduce Performance.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) with
CWE
Incorrect Control Flow Scoping
mitre_cwe·CVSS 7.4
[HIGH] CWE-705 Incorrect Control Flow Scoping
CWE-705: Incorrect Control Flow Scoping
The product does not properly return control flow to the proper location after it has completed a task or detected an unusual condition.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Alter Execution Logic, Other.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external comp
CWE
Incorrect Block Delimitation
mitre_cwe
CWE-483 Incorrect Block Delimitation
CWE-483: Incorrect Block Delimitation
The code does not explicitly delimit a block that is intended to contain 2 or more statements, creating a logic error.
In some languages, braces (or other delimiters) are optional for blocks. When the delimiter is omitted, it is possible to insert a logic error in which a statement is thought to be in a block but is not. In some cases, the logic error can have security implications.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Confidentiality, Integrity, Availability. Impact: Alter Execution Logic. This is a general logic error which will often lead to obviously-incorrect behaviors that are quickly noticed and fixed. In lightly tested or untested code, this error may be introduced it into a production environment and pro
CWE
Inappropriate Whitespace Style
mitre_cwe·CVSS 7.4
[HIGH] CWE-1114 Inappropriate Whitespace Style
CWE-1114: Inappropriate Whitespace Style
The source code contains whitespace that is inconsistent across
the code or does not follow expected standards for the
product.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Increase Analytical Complexity. A human auditor might indirectly trust that
whitespace (especially indentation) reflects the actual
control flow of the code, which could make it more
difficult to find vulnerabilities.
Scope: Other. Impact: Reduce Maintainability. This issue makes it more difficult to understand
and maintain the product, which indirectly affects
security by making it more difficult or time-consuming
to find and/or fix vulnerabilities.
Observed Examples:
CVE-2014-1266: Chain: incorrect "goto" in Apple SSL product bypas
CWE
Return of Wrong Status Code
mitre_cwe·CVSS 4.6
[MEDIUM] CWE-393 Return of Wrong Status Code
CWE-393: Return of Wrong Status Code
A function or operation returns an incorrect return value or status code that does not indicate the true result of execution, causing the product to modify its behavior based on the incorrect result.
This can lead to unpredictable behavior. If the function is used to make security-critical decisions or provide security-critical information, then the wrong status code can cause the product to assume that an action is safe or correct, even when it is not.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity, Other. Impact: Unexpected State, Alter Execution Logic. This weakness could place the system in a state that could lead unexpected logic to be executed or other unintended behaviors.
Detection Methods:
Fuzzing: Fuzz
CWE
Improper Certificate Validation
mitre_cwe
CWE-295 Improper Certificate Validation
CWE-295: Improper Certificate Validation
The product does not validate, or incorrectly validates, a certificate.
Background: A certificate is a token that associates an identity (principal) to a cryptographic key. Certificates can be used to check if a public key belongs to the assumed owner.
Modes of Introduction:
Phase: Architecture and Design
Phase: Implementation
Note: REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Phase: Implementation
Note: When the product uses certificate pinning, the developer might not properly validate all relevant components of the certificate before pinning the certificate. This can make it difficult or expensive to test after the pinning is complete.
Common Consequences:
Scope: Integrity, Authentication. Im
CWE
Insufficient Control Flow Management
mitre_cwe·CVSS 9.8
[CRITICAL] CWE-691 Insufficient Control Flow Management
CWE-691: Insufficient Control Flow Management
The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways.
Modes of Introduction:
Phase: Architecture and Design
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Alter Execution Logic.
Examples:
The following function attempts to acquire a lock in order to perform operations on a shared resource.
However, the code does not check the value returned by pthread_mutex_lock() for errors. If pthread_mutex_lock() cannot acquire the mutex for any reason, the function may introduce a race condition into the program and result in undefined behavior.
In order to avoid data races, correctly written programs must check the result of thread syn
CWE
Improper Restriction of Communication Channel to Intended Endpoints
mitre_cwe
CWE-923 Improper Restriction of Communication Channel to Intended Endpoints
CWE-923: Improper Restriction of Communication Channel to Intended Endpoints
The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.
Attackers might be able to spoof the intended endpoint from a different system or process, thus gaining the same level of access as the intended endpoint. While this issue frequently involves authentication between network-based clients and servers, other types of communication channels and endpoints can have this weakness.
Modes of Introduction:
Phase: Architecture and Design
Note: REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Common Consequences:
Scope: Integrity, C
http://it.slashdot.org/comments.pl?sid=4821073&cid=46310187http://support.apple.com/kb/HT6146http://support.apple.com/kb/HT6147http://support.apple.com/kb/HT6148http://support.apple.com/kb/HT6150https://news.ycombinator.com/item?id=7281378https://www.cs.columbia.edu/~smb/blog/2014-02/2014-02-23.htmlhttps://www.cs.columbia.edu/~smb/blog/2014-02/2014-02-24.htmlhttps://www.imperialviolet.org/2014/02/22/applebug.htmlhttp://it.slashdot.org/comments.pl?sid=4821073&cid=46310187http://support.apple.com/kb/HT6146http://support.apple.com/kb/HT6147http://support.apple.com/kb/HT6148http://support.apple.com/kb/HT6150https://news.ycombinator.com/item?id=7281378https://www.cs.columbia.edu/~smb/blog/2014-02/2014-02-23.htmlhttps://www.cs.columbia.edu/~smb/blog/2014-02/2014-02-24.htmlhttps://www.imperialviolet.org/2014/02/22/applebug.html
2014-02-22
Published