Summary: | archivers/libmspack: Update to 0.9.1 (Fixes several security vulnerabilities) | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Henry <PopularMoment> | ||||
Component: | Individual Port(s) | Assignee: | Ports Security Team <ports-secteam> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Many People | CC: | joneum, koobs, ports-secteam, swills | ||||
Priority: | Normal | Keywords: | needs-patch, security | ||||
Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(fjoe) koobs: maintainer-feedback? (ports-secteam) |
||||
Hardware: | Any | ||||||
OS: | Any | ||||||
URL: | https://www.cabextract.org.uk/libmspack/#vulns | ||||||
Attachments: |
|
Description
Henry
2018-12-09 19:44:06 UTC
Pending (requires) VuXML entry Committed, thanks! A commit references this bug: Author: fjoe Date: Tue Dec 11 08:44:00 UTC 2018 New revision: 487227 URL: https://svnweb.freebsd.org/changeset/ports/487227 Log: Update to 0.9.1alpha PR: 233896 Submitted by: Henry David Bartholomew Changes: head/archivers/libmspack/Makefile head/archivers/libmspack/distinfo Re-open for VuXML entry and MFH what is the current status? Does ports-secteam have to be active here? VuXML entries were not added for this (0.9.1) or previous releases The last libsmpack VuXML entry was <vuln vid="cc7548ef-06e1-11e5-8fda-002590263bf5"> added <entry>2015-05-31</entry> for version < 0.5 This leaves 10 CVE's (security vulnerabilities) not reported to users (per https://www.cabextract.org.uk/libmspack/#vulns) ping @fjoe Over to ports-secteam, no maintainer response since 2018-12-14 VuXML entries for latest and previous version vulnerabilities (At least 10) remains to be added After such a long time, I see no point in creating a vuxml entry. I'm closing here. @Jochen I don't understand how the time it has been is related or relevant to documenting known security vulnerabilities in VuXML? If this is a matter of limited available cycles at ports-secteam to document vulnerabilities (in this case > 10 of them), we can put a call out for others to contribute the change @Kubilay, I made this decision as ports-secteam. If you want to add the entry, please reopen this PR. Otherwise I consider it done. |