Skip to content

Commit 067a77a

Browse files
committed
Update metadata for Feb 11 release and security advisory
1 parent a597a77 commit 067a77a

File tree

3 files changed

+192
-0
lines changed

3 files changed

+192
-0
lines changed

newsflash.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,11 @@
11
| Date | Title |
22
| ----------- | ----- |
3+
| 11-Feb-2025 | [Security Advisory](/news/secadv/20250211.txt): one high severity fix |
4+
| 11-Feb-2025 | OpenSSL 3.4.1 is now available, including bug and security fixes |
5+
| 11-Feb-2025 | OpenSSL 3.3.3 is now available, including bug and security fixes |
6+
| 11-Feb-2025 | OpenSSL 3.2.4 is now available, including bug and security fixes |
7+
| 11-Feb-2025 | OpenSSL 3.1.8 is now available, including bug and security fixes |
8+
| 11-Feb-2025 | OpenSSL 3.0.16 is now available, including bug and security fixes |
39
| 20-Jan-2025 | [Security Advisory](/news/secadv/20250120.txt): one low severity fix. |
410
| 22-Oct-2024 | Final version of OpenSSL 3.4.0 is now available: please download and upgrade! |
511
| 16-Oct-2024 | [Security Advisory](/news/secadv/20241016.txt): one low severity fix. |

secadv/20250211.txt

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
OpenSSL Security Advisory [11th February 2025]
2+
==============================================
3+
4+
RFC7250 handshakes with unauthenticated servers don't abort as expected (CVE-2024-12797)
5+
========================================================================================
6+
7+
Severity: High
8+
9+
Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a
10+
server may fail to notice that the server was not authenticated, because
11+
handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode
12+
is set.
13+
14+
Impact summary: TLS and DTLS connections using raw public keys may be
15+
vulnerable to man-in-middle attacks when server authentication failure is not
16+
detected by clients.
17+
18+
RPKs are disabled by default in both TLS clients and TLS servers. The issue
19+
only arises when TLS clients explicitly enable RPK use by the server, and the
20+
server, likewise, enables sending of an RPK instead of an X.509 certificate
21+
chain. The affected clients are those that then rely on the handshake to
22+
fail when the server's RPK fails to match one of the expected public keys,
23+
by setting the verification mode to SSL_VERIFY_PEER.
24+
25+
Clients that enable server-side raw public keys can still find out that raw
26+
public key verification failed by calling SSL_get_verify_result(), and those
27+
that do, and take appropriate action, are not affected. This issue was
28+
introduced in the initial implementation of RPK support in OpenSSL 3.2.
29+
30+
The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
31+
OpenSSL 3.1, 3.0, 1.1.1 and 1.0.2 are also not affected by this issue.
32+
33+
OpenSSL 3.4, 3.3 and 3.2 are vulnerable to this issue.
34+
35+
OpenSSL 3.4 users should upgrade to OpenSSL 3.4.1.
36+
37+
OpenSSL 3.3 users should upgrade to OpenSSL 3.3.2.
38+
39+
OpenSSL 3.2 users should upgrade to OpenSSL 3.2.4.
40+
41+
This issue was reported on 18th December 2024 by Apple Inc.
42+
The fix was developed by Viktor Dukhovni.
43+
44+
General Advisory Notes
45+
======================
46+
47+
URL for this Security Advisory:
48+
https://openssl-library.org/news/secadv/20250211.txt
49+
50+
Note: the online version of the advisory may be updated with additional details
51+
over time.
52+
53+
For details of OpenSSL severity classifications please see:
54+
https://openssl-library.org/policies/general/security-policy/

secjson/CVE-2024-12797.json

Lines changed: 132 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,132 @@
1+
{
2+
"containers": {
3+
"cna": {
4+
"affected": [
5+
{
6+
"defaultStatus": "unaffected",
7+
"product": "OpenSSL",
8+
"vendor": "OpenSSL",
9+
"versions": [
10+
{
11+
"lessThan": "3.4.1",
12+
"status": "affected",
13+
"version": "3.4.0",
14+
"versionType": "semver"
15+
},
16+
{
17+
"lessThan": "3.3.3",
18+
"status": "affected",
19+
"version": "3.3.0",
20+
"versionType": "semver"
21+
},
22+
{
23+
"lessThan": "3.2.4",
24+
"status": "affected",
25+
"version": "3.2.0",
26+
"versionType": "semver"
27+
}
28+
]
29+
}
30+
],
31+
"credits": [
32+
{
33+
"lang": "en",
34+
"type": "finder",
35+
"value": "Apple Inc."
36+
},
37+
{
38+
"lang": "en",
39+
"type": "remediation developer",
40+
"value": "Viktor Dukhovni"
41+
}
42+
],
43+
"datePublic": "2025-02-11T14:00:00.000Z",
44+
"descriptions": [
45+
{
46+
"lang": "en",
47+
"supportingMedia": [
48+
{
49+
"base64": false,
50+
"type": "text/html",
51+
"value": "Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a<br>server may fail to notice that the server was not authenticated, because<br>handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode<br>is set.<br><br>Impact summary: TLS and DTLS connections using raw public keys may be<br>vulnerable to man-in-middle attacks when server authentication failure is not<br>detected by clients.<br><br>RPKs are disabled by default in both TLS clients and TLS servers. The issue<br>only arises when TLS clients explicitly enable RPK use by the server, and the<br>server, likewise, enables sending of an RPK instead of an X.509 certificate<br>chain. The affected clients are those that then rely on the handshake to<br>fail when the server's RPK fails to match one of the expected public keys,<br>by setting the verification mode to SSL_VERIFY_PEER.<br><br>Clients that enable server-side raw public keys can still find out that raw<br>public key verification failed by calling SSL_get_verify_result(), and those<br>that do, and take appropriate action, are not affected. This issue was<br>introduced in the initial implementation of RPK support in OpenSSL 3.2.<br><br>The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."
52+
}
53+
],
54+
"value": "Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a\nserver may fail to notice that the server was not authenticated, because\nhandshakes don't abort as expected when the SSL_VERIFY_PEER verification mode\nis set.\n\nImpact summary: TLS and DTLS connections using raw public keys may be\nvulnerable to man-in-middle attacks when server authentication failure is not\ndetected by clients.\n\nRPKs are disabled by default in both TLS clients and TLS servers. The issue\nonly arises when TLS clients explicitly enable RPK use by the server, and the\nserver, likewise, enables sending of an RPK instead of an X.509 certificate\nchain. The affected clients are those that then rely on the handshake to\nfail when the server's RPK fails to match one of the expected public keys,\nby setting the verification mode to SSL_VERIFY_PEER.\n\nClients that enable server-side raw public keys can still find out that raw\npublic key verification failed by calling SSL_get_verify_result(), and those\nthat do, and take appropriate action, are not affected. This issue was\nintroduced in the initial implementation of RPK support in OpenSSL 3.2.\n\nThe FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue."
55+
}
56+
],
57+
"metrics": [
58+
{
59+
"format": "other",
60+
"other": {
61+
"content": {
62+
"text": "High"
63+
},
64+
"type": "https://openssl-library.org/policies/general/security-policy/"
65+
}
66+
}
67+
],
68+
"problemTypes": [
69+
{
70+
"descriptions": [
71+
{
72+
"cweId": "CWE-392",
73+
"description": "CWE-392 Missing Report of Error Condition",
74+
"lang": "en",
75+
"type": "CWE"
76+
}
77+
]
78+
}
79+
],
80+
"providerMetadata": {
81+
"orgId": "00000000-0000-4000-9000-000000000000",
82+
"shortName": "openssl"
83+
},
84+
"references": [
85+
{
86+
"name": "OpenSSL Advisory",
87+
"tags": [
88+
"vendor-advisory"
89+
],
90+
"url": "https://openssl-library.org/news/secadv/20250211.txt"
91+
},
92+
{
93+
"name": "3.4.1 git commit",
94+
"tags": [
95+
"patch"
96+
],
97+
"url": "https://github.com/openssl/openssl/commit/738d4f9fdeaad57660dcba50a619fafced3fd5e9"
98+
},
99+
{
100+
"name": "3.3.3 git commit",
101+
"tags": [
102+
"patch"
103+
],
104+
"url": "https://github.com/openssl/openssl/commit/87ebd203feffcf92ad5889df92f90bb0ee10a699"
105+
},
106+
{
107+
"name": "3.2.4 git commit",
108+
"tags": [
109+
"patch"
110+
],
111+
"url": "https://github.com/openssl/openssl/commit/798779d43494549b611233f92652f0da5328fbe7"
112+
}
113+
],
114+
"source": {
115+
"discovery": "UNKNOWN"
116+
},
117+
"title": "RFC7250 handshakes with unauthenticated servers don't abort as expected",
118+
"x_generator": {
119+
"engine": "Vulnogram 0.2.0"
120+
}
121+
}
122+
},
123+
"cveMetadata": {
124+
"assignerOrgId": "00000000-0000-4000-9000-000000000000",
125+
"cveId": "CVE-2024-12797",
126+
"requesterUserId": "00000000-0000-4000-9000-000000000000",
127+
"serial": 1,
128+
"state": "PUBLISHED"
129+
},
130+
"dataType": "CVE_RECORD",
131+
"dataVersion": "5.1"
132+
}

0 commit comments

Comments
 (0)