To provide the utmost secure operating environment to Fedora and EPEL users.
If you need help or assistance with any issue, please feel free to contact the FST members at
- Mailing lists:-
- - Security Team mailing list
- - General security mailing list(good for questions)
- Weekly meetings:-
- Every Thurdays 14:00 UTC. -> Schedule and Agenda
What we do
Fedora Security Team aims to ensure that users are protected from any vulnerabilities that exist in Fedora packages. The vulnerabilities are reported to Fedora package maintainers via Bugzilla by Red Hat Product Security. These bugs are marked with keywords: SecurityTracking attribute in Bugzilla, for ex. => CVE-2013-0333 rubygem-activesupport: json to yaml parsing. The SecurityTracking keyword indicates that the bug could have security implications which need to be investigated. The package maintainer should then follow up with the upstream developers to obtain a patch or a new release which fixes the issue. Once such patch or a new release is available, the package maintainer then builds a new version of the package and submits an update to the Fedora or EPEL repositories via Bodhi.
It is a straight forward process. But the problems arise when package maintainers either don't understand the issue or are too busy to triage it. That is where the Fedora Security Team comes in to help. We work with the upstream developers to obtain the security fixes and help package maintainers to push these fixes to the Fedora repositories.
CVE stands for Common Vulnerabilities and Exposures and is the global standard for uniquely identifying and tracking software security vulnerabilities. Each vulnerability in any package has a unique CVE ID assigned to it. If it is a new security issue, we need to request a CVE ID for it from the oss-security mailing list. Alternatively, we may also request CVEs from Red Hat via email@example.com. CVE ID are allocated by the MITRE Corporation, which is the primary CVE Numbering Authority(CNA).
For each assigned CVE two bugs are created: one is the parent bug which describes the issue in human understandable details and lists available fixes and a second is the child bug which is used to track progression of these fixes into individual products(Fedora, Fedora-EPEL etc.). The parent bug is a generic one; it is opened against Component: vulnerability. Child bugs are specific; they are opened against Component: <package-name> of an individual product and are marked with keywords: SecurityTracking.
How to get involved
Joining the team
Joining the Fedora Security Team is easy. First, subscribe to the work flow and jump in. If you have questions please ask on IRC or on the mailing list.mailing list. Second, join us on the IRC channel. And third, read the
- Select an open security bug from -> Open issues.
- Own the bug.
- Examine the bug details and validate if it is really a security issue.
- Determine if a fix is available and if the vulnerability is already fixed in Fedora by examining the current version and/or talking with the package maintainer.
- If a fix is not available, work with the upstream developers via bug tracking/mailing list/IRC channels to obtain a patch or new version which fixes the issue.
- Work with the package maintainer to get patch or fixed version packaged and pushed as a security update.
- GOTO 1;
You can log your 90-day Security Challenge work in the ethercalc spreadsheet.
If you run into a nonresponsive package maintainer we do follow Release Engineering policy.
Each tracking bug should have an owner for several reasons. It would certainly be inefficient if the work was done twice. At times collisions and misunderstandings might occur if two people tried to coordinate a fix with an upstream developer independently. For these reasons, we should indicate the fact that we are working on the tracking bug by filling the Whiteboard of the bug with Bugzilla user name of the owner:
As <owner> FAS ID should be used; It simplifies further management. For the list of Bugzilla user names of the Fedora Security Team see the Security Team Roster.
Note: For multiple FST owners FAS IDs should be comma-separated and NOT contain spaces.
- Open issues