View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002999 | Kali Linux | Kali Package Bug | public | 2016-01-18 17:03 | 2020-12-01 10:48 |
Reporter | ElColmo | Assigned To | rhertzog | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 2.0 | ||||
Fixed in Version | 2016.1 | ||||
Summary | 0002999: Kali 2.0 uses a version of libnss3 that is prone to using weaker/older SSL certificates in certain circumstances | ||||
Description | Kali 2.0 uses a version of libnss3 that is prone to using weaker/older certs, when navigating up the CA chain. One fairly obvious impact is that Google Chromium incorrectly displays the HTTPS symbol in red, rather than in green, since it uses the less secure SHA-1 based path, rather than the more secure SHA-2 based path, where multiple paths exist. This appears to be an issue where "cross-signed" roots are used, for instance. See https://sslmate.com/blog/post/chrome_cached_sha1_chains for more details. The bug in question is present in nss_3.17.2-1.1+deb8u1, but is resolved in nss_3.17.2-1.1+deb8u2. Please see: | ||||
Steps To Reproduce | #0: Verify "nss_3.17.2-1.1+deb8u1" is installed | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2016-01-18 17:03 | ElColmo | New Issue | |
2016-01-22 08:09 | rhertzog | Note Added: 0004534 | |
2016-01-22 08:09 | rhertzog | Status | new => resolved |
2016-01-22 08:09 | rhertzog | Fixed in Version | => 2016.1 |
2016-01-22 08:09 | rhertzog | Resolution | open => fixed |
2016-01-22 08:09 | rhertzog | Assigned To | => rhertzog |
2020-12-01 10:48 | g0tmi1k | Priority | high => normal |