Bug 655018

Summary: CVE-2010-4177 CVE-2010-4178 mysql-gui-tools various flaws [fedora-12]
Product: [Fedora] Fedora Reporter: Jan Lieskovsky <jlieskov>
Component: mysql-gui-toolsAssignee: Dennis Gilmore <dennis>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 12CC: dennis, pahan
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Release Note
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 12:00:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 655012, 655015    

Description Jan Lieskovsky 2010-11-19 11:25:50 UTC
fedora-12 tracking bug for mysql-gui-tools: see blocks bug list for full details of the security issue(s).

This bug is never intended to be made public, please put any public notes
in the 'blocks' bugs.


[bug automatically created by: add-tracking-bugs]

Comment 1 Jan Lieskovsky 2010-11-19 11:26:14 UTC
    Adding parent bug CVE-2010-4178
    New bodhi update url:
    https://admin.fedoraproject.org/updates/new/?type_=security&bugs=655015,655012

Comment 2 Pavel Alexeev 2010-11-19 17:08:43 UTC
musql-gui-tools is dead package. It is not supported upstream many times and it is not Fedora start from 13. I do not want even see on it. Fedora 12 in few days reached EOL. So, I suggest close it.

Comment 3 Bug Zapper 2010-12-03 12:00:23 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.