chromium-browser: issue with spake implementation in boringssl
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | Google Chrome prior to 63.0.3239.84 unknown | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 6 Supplementary | |||
| chromium-browser-0:63.0.3239.84-1.el6_9 | cpe:/a:redhat:rhel_extras:6 | RHSA-2017:3401 | 2017-12-07T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-4064-1 | chromium-browser security update |
EUVD |
EUVD-2017-6875 | Inappropriate implementation in BoringSSL SPAKE2 in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to leak the low-order bits of SHA512(password) by inspecting protocol traffic. |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 1.5% (1.513% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.