-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update module golang.org/x/crypto to v0.17.0 [security] - autoclosed #57
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to e984872 [security]
fix(deps): update golang.org/x/crypto digest to 3f8f064 [security]
Jul 18, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
July 18, 2023 08:54
9f8edb0
to
6c18d8b
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 3f8f064 [security]
fix(deps): update golang.org/x/crypto digest to e984872 [security]
Jul 19, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
July 19, 2023 17:46
6c18d8b
to
065c228
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to e984872 [security]
fix(deps): update golang.org/x/crypto digest to 12e1fcd [security]
Jul 21, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
July 21, 2023 05:37
065c228
to
6be9fdb
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 12e1fcd [security]
fix(deps): update golang.org/x/crypto digest to e984872 [security]
Jul 22, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
July 22, 2023 02:32
6be9fdb
to
d039d18
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to e984872 [security]
fix(deps): update golang.org/x/crypto digest to d08e19b [security]
Jul 30, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
July 30, 2023 02:11
d039d18
to
1d24ed6
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to d08e19b [security]
fix(deps): update golang.org/x/crypto digest to e984872 [security]
Jul 31, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
July 31, 2023 06:00
1d24ed6
to
cb9159a
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to e984872 [security]
fix(deps): update golang.org/x/crypto digest to b4ddeed [security]
Aug 7, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
August 7, 2023 02:25
cb9159a
to
d49be0c
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to b4ddeed [security]
fix(deps): update golang.org/x/crypto digest to 0d375be [security]
Sep 5, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
September 5, 2023 17:54
d49be0c
to
35c39df
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 0d375be [security]
fix(deps): update golang.org/x/crypto digest to d359caa [security]
Sep 6, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
September 6, 2023 23:54
35c39df
to
a572b0f
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to d359caa [security]
fix(deps): update golang.org/x/crypto digest to 0d375be [security]
Sep 7, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
September 7, 2023 11:54
a572b0f
to
2ee2056
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 0d375be [security]
fix(deps): update golang.org/x/crypto digest to e90f1e1 [security]
Sep 8, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
September 8, 2023 05:16
2ee2056
to
8f259df
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to e90f1e1 [security]
fix(deps): update golang.org/x/crypto digest to 0d375be [security]
Sep 9, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
September 9, 2023 14:34
8f259df
to
b1c438f
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 0d375be [security]
fix(deps): update golang.org/x/crypto digest to 3f0842a [security]
Sep 12, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
September 12, 2023 02:54
b1c438f
to
2980298
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 3f0842a [security]
fix(deps): update golang.org/x/crypto digest to 0d375be [security]
Sep 14, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
September 14, 2023 20:46
2980298
to
4055639
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 1cf1811 [security]
fix(deps): update golang.org/x/crypto digest to eb61739 [security]
Nov 13, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
November 13, 2023 02:56
3240416
to
3fcb1d9
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to eb61739 [security]
fix(deps): update golang.org/x/crypto digest to 1cf1811 [security]
Nov 20, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
November 20, 2023 08:24
3fcb1d9
to
66c2c86
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 1cf1811 [security]
fix(deps): update golang.org/x/crypto digest to eb61739 [security]
Nov 21, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
November 21, 2023 02:52
66c2c86
to
b7e79c9
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to eb61739 [security]
fix(deps): update golang.org/x/crypto digest to 270bf25 [security]
Nov 22, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
November 22, 2023 17:50
b7e79c9
to
bcf643a
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 270bf25 [security]
fix(deps): update golang.org/x/crypto digest to eb61739 [security]
Nov 23, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
November 23, 2023 05:17
bcf643a
to
dbb69a6
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to eb61739 [security]
fix(deps): update golang.org/x/crypto digest to 325b735 [security]
Nov 28, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
November 28, 2023 02:54
dbb69a6
to
00b4fb6
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 325b735 [security]
fix(deps): update golang.org/x/crypto digest to 152cdb1 [security]
Nov 30, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
November 30, 2023 08:33
00b4fb6
to
0d0f27e
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 152cdb1 [security]
fix(deps): update golang.org/x/crypto digest to 325b735 [security]
Dec 6, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
December 6, 2023 02:35
0d0f27e
to
4b72420
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 325b735 [security]
fix(deps): update golang.org/x/crypto digest to 152cdb1 [security]
Dec 9, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
December 9, 2023 05:55
4b72420
to
60e8fc6
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 152cdb1 [security]
fix(deps): update golang.org/x/crypto digest to 325b735 [security]
Dec 11, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
December 11, 2023 05:05
60e8fc6
to
0070adf
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 325b735 [security]
fix(deps): update golang.org/x/crypto digest to 4e5a261 [security]
Dec 15, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
December 15, 2023 17:47
0070adf
to
03b991a
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 4e5a261 [security]
fix(deps): update golang.org/x/crypto digest to 325b735 [security]
Dec 16, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
December 16, 2023 08:38
03b991a
to
d469326
Compare
renovate
bot
changed the title
fix(deps): update golang.org/x/crypto digest to 325b735 [security]
fix(deps): update module golang.org/x/crypto to v0.17.0 [security]
Dec 19, 2023
renovate
bot
force-pushed
the
renovate/go-golang.org/x/crypto-vulnerability
branch
from
December 19, 2023 05:29
d469326
to
9b89bfb
Compare
renovate
bot
changed the title
fix(deps): update module golang.org/x/crypto to v0.17.0 [security]
fix(deps): update module golang.org/x/crypto to v0.17.0 [security] - autoclosed
Jan 30, 2024
renovate
bot
deleted the
renovate/go-golang.org/x/crypto-vulnerability
branch
January 30, 2024 23:59
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.0.0-20191206172530-e9b2fee46413
->v0.17.0
GitHub Vulnerability Alerts
CVE-2020-9283
golang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client.
CVE-2020-7919
The Helm core maintainers have identified a high severity security vulnerability in Go's
crypto
package affecting all versions prior to Helm 2.16.8 and Helm 3.1.0.Thanks to @ravin9249 for identifying the vulnerability.
Impact
Go before 1.12.16 and 1.13.x before 1.13.7 (and the
crypto/cryptobyte
package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients resulting in a panic via a malformed X.509 certificate. This may allow a remote attacker to cause a denial of service.Patches
A patch to compile Helm against Go 1.14.4 has been provided for Helm 2 and is available in Helm 2.16.8. Helm 3.1.0 and newer are compiled against Go 1.13.7+.
Workarounds
No workaround is available. Users are urged to upgrade.
References
For more information
If you have any questions or comments about this advisory:
CVE-2022-27191
The golang.org/x/crypto/ssh package before 0.0.0-20220314234659-1baeb1ce4c0b for Go allows an attacker to crash a server in certain circumstances involving AddHostKey.
CVE-2021-43565
The x/crypto/ssh package before 0.0.0-20211202192323-5770296d904e of golang.org/x/crypto allows an unauthenticated attacker to panic an SSH server. When using AES-GCM or ChaCha20Poly1305, consuming a malformed packet which contains an empty plaintext causes a panic.
CVE-2020-29652
A nil pointer dereference in the golang.org/x/crypto/ssh component through v0.0.0-20201203163018-be400aefbc4c for Go allows remote attackers to cause a denial of service against SSH servers. An attacker can craft an authentication request message for the
gssapi-with-mic
method which will cause NewServerConn to panic via a nil pointer dereference if ServerConfig.GSSAPIWithMICConfig is nil.CVE-2023-48795
Summary
Terrapin is a prefix truncation attack targeting the SSH protocol. More precisely, Terrapin breaks the integrity of SSH's secure channel. By carefully adjusting the sequence numbers during the handshake, an attacker can remove an arbitrary amount of messages sent by the client or server at the beginning of the secure channel without the client or server noticing it.
Mitigations
To mitigate this protocol vulnerability, OpenSSH suggested a so-called "strict kex" which alters the SSH handshake to ensure a Man-in-the-Middle attacker cannot introduce unauthenticated messages as well as convey sequence number manipulation across handshakes.
Warning: To take effect, both the client and server must support this countermeasure.
As a stop-gap measure, peers may also (temporarily) disable the affected algorithms and use unaffected alternatives like AES-GCM instead until patches are available.
Details
The SSH specifications of ChaCha20-Poly1305 (chacha20-poly1305@openssh.com) and Encrypt-then-MAC (*[email protected] MACs) are vulnerable against an arbitrary prefix truncation attack (a.k.a. Terrapin attack). This allows for an extension negotiation downgrade by stripping the SSH_MSG_EXT_INFO sent after the first message after SSH_MSG_NEWKEYS, downgrading security, and disabling attack countermeasures in some versions of OpenSSH. When targeting Encrypt-then-MAC, this attack requires the use of a CBC cipher to be practically exploitable due to the internal workings of the cipher mode. Additionally, this novel attack technique can be used to exploit previously unexploitable implementation flaws in a Man-in-the-Middle scenario.
The attack works by an attacker injecting an arbitrary number of SSH_MSG_IGNORE messages during the initial key exchange and consequently removing the same number of messages just after the initial key exchange has concluded. This is possible due to missing authentication of the excess SSH_MSG_IGNORE messages and the fact that the implicit sequence numbers used within the SSH protocol are only checked after the initial key exchange.
In the case of ChaCha20-Poly1305, the attack is guaranteed to work on every connection as this cipher does not maintain an internal state other than the message's sequence number. In the case of Encrypt-Then-MAC, practical exploitation requires the use of a CBC cipher; while theoretical integrity is broken for all ciphers when using this mode, message processing will fail at the application layer for CTR and stream ciphers.
For more details see https://terrapin-attack.com.
Impact
This attack targets the specification of ChaCha20-Poly1305 (chacha20-poly1305@openssh.com) and Encrypt-then-MAC (*[email protected]), which are widely adopted by well-known SSH implementations and can be considered de-facto standard. These algorithms can be practically exploited; however, in the case of Encrypt-Then-MAC, we additionally require the use of a CBC cipher. As a consequence, this attack works against all well-behaving SSH implementations supporting either of those algorithms and can be used to downgrade (but not fully strip) connection security in case SSH extension negotiation (RFC8308) is supported. The attack may also enable attackers to exploit certain implementation flaws in a man-in-the-middle (MitM) scenario.
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.