AVG-611 - log back

AVG-611 edited at 17 Nov 2021 10:35:01
Advisory qualified
- Yes
+ No
AVG-611 edited at 04 Nov 2021 09:35:42
Status
- Testing
+ Fixed
AVG-611 edited at 03 Nov 2021 13:57:29
Status
- Vulnerable
+ Testing
Fixed
+ 6.0-15
Ticket
- 69739
AVG-611 edited at 03 Nov 2021 13:55:35
Issues
CVE-2014-9913
CVE-2016-9844
CVE-2018-18384
CVE-2018-1000035
+ CVE-2019-13232
AVG-611 edited at 03 Nov 2021 13:43:08
Severity
- Low
+ Medium
AVG-611 edited at 03 Nov 2021 13:41:05
Issues
+ CVE-2014-9913
CVE-2016-9844
CVE-2018-18384
CVE-2018-1000035
AVG-611 edited at 03 Nov 2021 13:36:25
Issues
+ CVE-2016-9844
+ CVE-2018-18384
CVE-2018-1000035
AVG-611 edited at 23 Feb 2021 11:27:47
Ticket
+ 69739
Notes
- Still no fix upstream. We do use FORTIFY_SOURCE=2 on our builds and that works as a "workaround" since it kills the app. Perhaps we should downgrade the severity and set the impact to DoS?
AVG-611 edited at 24 Apr 2020 16:59:21
Affected
- 6.0-13
+ 6.0-14
AVG-611 created at 25 Sep 2019 19:31:50
Packages
+ unzip
Issues
+ CVE-2018-1000035
Status
+ Vulnerable
Severity
+ Low
Affected
+ 6.0-13
Fixed
Ticket
Advisory qualified
+ Yes
References
Notes
+ Still no fix upstream. We do use FORTIFY_SOURCE=2 on our builds and that works as a "workaround" since it kills the app. Perhaps we should downgrade the severity and set the impact to DoS?