Advisories » MGASA-2018-0024

Updated w3m packages fix security vulnerability

Publication date: 03 Jan 2018
Modification date: 03 Jan 2018
Type: security
Affected Mageia releases : 5
CVE: CVE-2016-9422 , CVE-2016-9423 , CVE-2016-9424 , CVE-2016-9425 , CVE-2016-9426 , CVE-2016-9427 , CVE-2016-9428 , CVE-2016-9429 , CVE-2016-9430 , CVE-2016-9431 , CVE-2016-9432 , CVE-2016-9433 , CVE-2016-9434 , CVE-2016-9435 , CVE-2016-9436 , CVE-2016-9437 , CVE-2016-9438 , CVE-2016-9439 , CVE-2016-9440 , CVE-2016-9441 , CVE-2016-9442 , CVE-2016-9443 , CVE-2016-9622 , CVE-2016-9623 , CVE-2016-9624 , CVE-2016-9625 , CVE-2016-9626 , CVE-2016-9627 , CVE-2016-9628 , CVE-2016-9629 , CVE-2016-9630 , CVE-2016-9631 , CVE-2016-9632 , CVE-2016-9633

Description

The w3m package has been updated to a newer git snapshot to fix several
security issues.
                

References

• https://bugs.mageia.org/show_bug.cgi?id=19811
• http://www.openwall.com/lists/oss-security/2016/11/03/3
• http://openwall.com/lists/oss-security/2016/11/24/1
• http://openwall.com/lists/oss-security/2016/11/25/5
• https://lists.opensuse.org/opensuse-updates/2016-12/msg00084.html
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9422
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9423
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9424
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9425
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9426
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9427
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9428
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9429
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9430
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9431
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9432
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9433
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9434
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9435
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9436
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9437
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9438
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9439
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9440
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9441
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9442
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9443
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9622
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9623
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9624
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9625
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9626
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9627
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9628
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9629
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9630
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9631
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9632
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9633

SRPMS

5/core

• w3m-0.5.3-8.2.mga5