Описание
Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would b...
| Релиз | Статус | Примечание |
|---|---|---|
| devel | needed | |
| esm-apps/bionic | released | 1:0.0~git20170629.0.5ef0053-2ubuntu0.1~esm1 |
| esm-apps/focal | released | 1:0.0~git20200221.2aa609c-1ubuntu0.1~esm1 |
| esm-apps/jammy | released | 1:0.0~git20211202.5770296-1ubuntu0.1~esm1 |
| esm-apps/noble | released | 1:0.19.0-1ubuntu0.1~esm1 |
| esm-infra/xenial | released | 1:0.0~git20151201.0.7b85b09-2ubuntu0.1~esm1 |
| focal | ignored | end of standard support, was needs-triage |
| jammy | needed | |
| noble | needed | |
| oracular | ignored | end of life, was needs-triage |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | 20250506.01-0ubuntu1 |
| esm-apps/bionic | released | 20241011.01-0ubuntu1~18.04.0+esm1 |
| esm-apps/xenial | released | 20240716.00-0ubuntu1~16.04.0+esm1 |
| esm-infra/focal | released | 20250116.00-0ubuntu1~20.04.0+esm1 |
| jammy | released | 20250116.00-0ubuntu1~22.04.1 |
| noble | released | 20250116.00-0ubuntu1~24.04.2 |
| plucky | released | 20250116.00-0ubuntu2.1 |
| questing | not-affected | 20250506.01-0ubuntu1 |
| upstream | released | 20250506.01 |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | DNE | |
| esm-apps/focal | not-affected | code-not-present |
| esm-infra/bionic | needs-triage | |
| esm-infra/xenial | needs-triage | |
| focal | not-affected | code-not-present |
| jammy | DNE | |
| noble | DNE | |
| oracular | DNE | |
| plucky | DNE | |
| questing | DNE |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | code not present |
| esm-infra/bionic | not-affected | code not present |
| esm-infra/focal | not-affected | code not present |
| esm-infra/xenial | not-affected | code not present |
| focal | not-affected | code not present |
| jammy | not-affected | code not present |
| noble | not-affected | code not present |
| oracular | not-affected | code not present |
| plucky | not-affected | code not present |
| questing | not-affected | code not present |
Показывать по
Ссылки на источники
EPSS
9.1 Critical
CVSS3
Связанные уязвимости
Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would b...
Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be c
Applications and libraries which misuse connection.serverAuthenticate ...
EPSS
9.1 Critical
CVSS3