Identify CVE (Common Vulnerabilities and Exposures) in Iggy #3678
Replies: 2 comments 1 reply
-
|
Initial audit scan found the below issues. Two useful urls - https://rustsec.org/, https://rustsec.org/advisories/ ========== Crate: quick-xml Crate: quick-xml Crate: quick-xml Crate: quick-xml Crate: quick-xml Crate: quick-xml Crate: rsa Crate: atomic-polyfill Crate: bincode Crate: paste Crate: proc-macro-error Crate: proc-macro-error2 Crate: rustls-pemfile Crate: rustybuzz Crate: ttf-parser Crate: anyhow Crate: spin |
Beta Was this translation helpful? Give feedback.
-
|
Based on the analysis, I am creating 3 GH Issues.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Background : Late 2020 or Early2021, the entire Enterprise software community went into panic mode due to Log4j vulnerability, resulting in remediating and preventing security issues. This resulted in significant importance to organizing categorizing in CVEs
Managing Common Vulnerabilities and Exposures (CVEs) is a critical security requirement for all enterprise-grade software. This discussion is to find out Iggy's CVEs compliance and document the process to flag and remediate any potential issues. One way to identify CVEs is to have a git pre-merge checks. Below are some of the options. I would like community's thoughts around this topic.
cargo-audit: Automatically audits Cargo.lock file for crates with known security vulnerabilities. It integrates easily into CI/CD workflows via the cargo-audit GitHub Action.
cargo-deny: A highly configurable linter that checks entire dependency graph. In addition to scanning for vulnerabilities, it enforces rules on open-source licenses, bans specific crates, and catches duplicate dependency versions.
cargo-auditable: Embeds the complete dependency tree directly into compiled Rust binaries. This allows production binaries to be scanned for CVEs post-deployment using cargo-audit, even if the source code or lockfile is no longer available..
Beta Was this translation helpful? Give feedback.
All reactions