mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-04 10:40:34 +01:00
ac125ee29a
As proposed in #240 and tracked in #414, this PR translates all advisories into the new "V3" advisory format, which is based on Markdown with leading TOML front matter. This format makes it easier to see rendered Markdown syntax descriptions, whether rendered by an IDE or GitHub. This should help with both crafting advisories initially as well as review, and ideally encourages more lengthy descriptions. Support for this format shipped in `cargo-audit` v0.12.0 on May 6th, 2020.
26 lines
884 B
Markdown
26 lines
884 B
Markdown
```toml
|
|
[advisory]
|
|
id = "RUSTSEC-2016-0001"
|
|
package = "openssl"
|
|
aliases = ["CVE-2016-10931"]
|
|
date = "2016-11-05"
|
|
keywords = ["ssl", "mitm"]
|
|
url = "https://github.com/sfackler/rust-openssl/releases/tag/v0.9.0"
|
|
[versions]
|
|
patched = [">= 0.9.0"]
|
|
```
|
|
|
|
# SSL/TLS MitM vulnerability due to insecure defaults
|
|
|
|
All versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults
|
|
including off-by-default certificate verification and no API to perform hostname
|
|
verification.
|
|
|
|
Unless configured correctly by a developer, these defaults could allow an attacker
|
|
to perform man-in-the-middle attacks.
|
|
|
|
The problem was addressed in newer versions by enabling certificate verification
|
|
by default and exposing APIs to perform hostname verification. Use the
|
|
`SslConnector` and `SslAcceptor` types to take advantage of these new features
|
|
(as opposed to the lower-level `SslContext` type).
|