mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-02-23 15:38:27 +01:00
782efebde9
This reverts commit 0a981e2b6f.
These now need to use the new `affected_paths` attribute, which has a
different (VersionReq-bucketed) format.
23 lines
846 B
TOML
23 lines
846 B
TOML
[advisory]
|
|
id = "RUSTSEC-2018-0001"
|
|
package = "untrusted"
|
|
unaffected_versions = []
|
|
patched_versions = [">= 0.6.2"]
|
|
url = "https://github.com/briansmith/untrusted/pull/20"
|
|
keywords = ["crash"]
|
|
title = "An integer underflow could lead to panic"
|
|
date = "2018-06-21"
|
|
description = """
|
|
A mistake in error handling in untrusted before 0.6.2 could lead to an integer
|
|
underflow and panic if a user of the crate didn't properly check for errors
|
|
returned by untrusted.
|
|
|
|
Combination of these two programming errors (one in untrusted and another by
|
|
user of this crate) could lead to a panic and maybe a denial of service of
|
|
affected software.
|
|
|
|
The error in untrusted is fixed in release 0.6.2 released 2018-06-21. It's also
|
|
advisable that users of untrusted check for their sources for cases where errors
|
|
returned by untrusted are not handled correctly.
|
|
"""
|