-
Notifications
You must be signed in to change notification settings - Fork 118
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
cargo-deny panicked when trying to check advisories.
To Reproduce
Steps to reproduce the behavior:
- cargo install cargo-deny
- git clone git@github.com:cortex/ripasso.git
- cd ripasso
- cargo deny check advisories
Expected behavior
Get a list of security problems
Instead got this output:
2020-02-02 15:53:48 [WARN] config path '/tmp/ripasso/deny.toml' doesn't exist, falling back to default config
thread '<unnamed>' panicked at 'internal error: entered unreachable code: the advisory database report contained an advisory
that somehow matched a crate we don't know about:
Metadata {
id: Id {
kind: RUSTSEC,
year: Some(
2019,
),
string: "RUSTSEC-2019-0006",
},
package: Name(
"ncurses",
),
date: Date(
"2019-06-15",
),
aliases: [],
references: [],
collection: Some(
Crates,
),
categories: [],
keywords: [],
cvss: None,
informational: None,
obsolete: false,
url: Some(
"https://github.com/RustSec/advisory-db/issues/106",
),
title: "Buffer overflow and format vulnerabilities in functions exposed without unsafe",
description: "`ncurses` exposes functions from the ncurses library which:\n\n- Pass buffers without length to C functions that may write an arbitrary amount of\n data, leading to a buffer overflow. (`instr`, `mvwinstr`, etc)\n- Passes rust &str to strings expecting C format arguments, allowing hostile\n input to execute a format string attack, which trivially allows writing\n arbitrary data to stack memory (functions in the `printw` family).\n",
patched_versions: [],
unaffected_versions: [],
}', /home/capitol/.cargo/registry/src/github.liu-huaimin.workers.dev-1ecc6299db9ec823/cargo-deny-0.6.2/src/advisories/mod.rs:229:17
stack backtrace:
0: std::sys_common::backtrace::print
1: std::panicking::default_hook::{{closure}}
2: std::panicking::default_hook
3: std::panicking::rust_panic_with_hook
4: std::panicking::continue_panic_fmt
5: std::panicking::begin_panic_fmt
6: cargo_deny::advisories::check::{{closure}}
7: cargo_deny::advisories::check
8: <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
9: std::panicking::try::do_call
10: __rust_maybe_catch_panic
11: <rayon_core::job::HeapJob<BODY> as rayon_core::job::Job>::execute
12: rayon_core::registry::WorkerThread::wait_until_cold
13: rayon_core::registry::ThreadBuilder::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Device:
- OS: Ubuntu 19.10
- Version 0.6.2
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working