Salvatore Bonaccorso pushed to branch master at Debian Security Tracker / 
security-tracker


Commits:
db35dd30 by Salvatore Bonaccorso at 2018-02-03T08:44:22+01:00
Add CVE-2018-1000030/python

Note: although the upstream bug claims that the Python 3.x is
implemented different and more safely, still some versions segfault,
thus need proper investigation before marking 3.x versions as
not-affected.

- - - - -


1 changed file:

- data/CVE/list


Changes:

=====================================
data/CVE/list
=====================================
--- a/data/CVE/list
+++ b/data/CVE/list
@@ -575,6 +575,17 @@ CVE-2018-6377 (In Joomla! before 3.8.4, inadequate input 
filtering in com_fields
        NOT-FOR-US: Joomla!
 CVE-2018-6376 (In Joomla! before 3.8.4, the lack of type casting of a variable 
in a ...)
        NOT-FOR-US: Joomla!
+CVE-2018-1000030 [Heap-Buffer-Overflow and Heap-Use-After-Free in 
Objects/fileobject.c]
+       - python3.7 <unfixed>
+       - python3.6 <unfixed>
+       - python3.5 <unfixed>
+       - python3.4 <removed>
+       - python3.2 <removed>
+       - python2.7 <unfixed>
+       - python2.6 <removed>
+       NOTE: https://bugs.python.org/issue31530
+       NOTE: 
https://bugs.python.org/file47157/0001-stop-crashes-when-iterating-over-a-file-on-multiple-.patch
+       TODO: check, although claimed that Python 3.x is implemented safely, 
some versions still segfault, thus need proper investigation.
 CVE-2018-1000029
        RESERVED
 CVE-2018-1000026



View it on GitLab: 
https://salsa.debian.org/security-tracker-team/security-tracker/commit/db35dd3063f118818e834e31a07c220aef084aac

---
View it on GitLab: 
https://salsa.debian.org/security-tracker-team/security-tracker/commit/db35dd3063f118818e834e31a07c220aef084aac
You're receiving this email because of your account on salsa.debian.org.
_______________________________________________
Secure-testing-commits mailing list
Secure-testing-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/secure-testing-commits

Reply via email to