OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2026-01-21 02:51:04 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
00a4c19a4608a5010260bf3bf8e7b1e53e008bf2
advisory-db/crates/libsecp256k1/RUSTSEC-2019-0027.md
Tony Arcieri ac125ee29a Translate database into V3 advisory format (#420) 
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.
2020-10-01 18:29:11 -07:00

609 B
Raw Blame History 

[advisory]
id = "RUSTSEC-2019-0027"
package = "libsecp256k1"
categories = ["crypto-failure"]
date = "2019-10-14"
keywords = ["crypto", "sidechannel"]

[affected.functions]
"libsecp256k1::Scalar::check_overflow" = ["< 0.3.1"]

[versions]
patched = [">= 0.3.1"]

Flaw in Scalar::check_overflow allows side-channel timing attack

Versions of libsecp256k1 prior to 0.3.1 did not execute Scalar::check_overflow in constant time.

This allows an attacker to potentially leak information via a timing attack.

The flaw was corrected by modifying Scalar::check_overflow to execute in constant time.