Backport #41309 ( 8b281f83e ) to fix use of uninitialized data.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
freetype (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned | ||
Utopic |
Won't Fix
|
Undecided
|
Unassigned | ||
Vivid |
Fix Released
|
Undecided
|
Unassigned | ||
Wily |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
FreeType issue https:/
This is a request to backport http://
information type: | Private Security → Public Security |
Changed in freetype (Ubuntu Precise): | |
status: | New → Confirmed |
Changed in freetype (Ubuntu Trusty): | |
status: | New → Confirmed |
Changed in freetype (Ubuntu Utopic): | |
status: | New → Confirmed |
Changed in freetype (Ubuntu Vivid): | |
status: | New → Confirmed |
Changed in freetype (Ubuntu Wily): | |
status: | New → Confirmed |
Changed in freetype (Ubuntu Utopic): | |
status: | Confirmed → Won't Fix |
Changed in freetype (Ubuntu Trusty): | |
assignee: | nobody → lava (lavasanjay) |
Changed in freetype (Ubuntu Trusty): | |
assignee: | lava (lavasanjay) → nobody |
Not sure how much it helps, but here is the git format-patch I made locally against the source of precise-security freetype 2.4.8-1ubuntu2.2 . I haven't patched the current Trusty freetype, but I have verified that it doesn't have the fix yet.