Projects In order to improve the security of the ONAP code base, projects are to focus on upgrading the third party packages that are direct dependencies. This change has been implemented in the Frankfurt release. Previous releases required vulnerability analysis in addition to the latest version at M2.package upgrades. Beginning with the Frankfurt release, the remediation of known vulnerabilities in third party packages will be managed as follows.
- Changes from Remediating Known Vulnerabilities in Third Party Packages in the Beijing through El Alto releases
- There is no
- requirement to provide effective/ineffective analysis until there are tools to support the analysis
- .
- There is no requirement to create vulnerability review tables.
- M2Projects update direct dependencies in their applications to most recent version of packages
- Projects identify the direct dependencies (packages) in each project component.
- NexusIQ provides a list of all packages used in a component.
- Maven creates dependency tree that identifies direct dependencies as the "left-most packages".
- Projects identify the most recent version of the direct dependencies
- Tools to help choose the upgrade version
- NexusIQ
- Maven (https://mvnrepository.com)
- Tools to help choose the upgrade version
- SECCOM updates oparent.pom to include the most recent version of included packages that are available at M2.
- Each project opens Jiras tickets Projects open Jiras to update older package versions in direct dependencies and commit to upgrading by M4
- NexusIQ provides package history - SECCOM recommendation is to use the latest GA release of a package available at M2
- Include the new version number in the Jira ticket
- No requirement to upgrade transitive dependent packages
- Projects identify the direct dependencies (packages) in each project component.
- SECCOM will update oparent to include the most recent version of included packages as of the time of the oparent release for the ONAP release (mid December) All known CVEs for each component will be listed in readthedocs for the release with no analysis
- .
- Note: There is no requirement to upgrade transitive dependent packages.
- There must be a separate Jira for each package to be upgraded in each project repository.
- Required information in Jira ticket:
- Old and new version numbers
- Label of "ComponentUpgrade"
- Fix Version = release under development
- Exceptions: The project must request a TSC exception for each direct dependency that cannot be upgraded by M4.
- Required information in the "ComponentUpgrade" Jira ticket with an exception:
- The reason that the package cannot be upgraded,
- Fix Version = the next release to be developed
- Required information in the "ComponentUpgrade" Jira ticket with an exception:
- .
- M4
- Project will close each Jira ticket that has been completed.
- SECCOM will create a report of the status of all "ComponentUpgrade" Jiras for the release.
- Open tickets will require a TSC exception
- Jiras with M4 exceptions must contain the same information documented above
- Readthedocs
- All projects will list all CVEs (CVE number only) associated with third party packages in the readthedocs in the Third Party Vulnerabilities section.
- Vulnerabilities are listed in the NexusIQ reports for each project repository scanned
- All projects will list all CVEs (CVE number only) associated with third party packages in the readthedocs in the Third Party Vulnerabilities section.
The CLAMP team will investigate writing a script to automatically generate project-level Jira tickets for all direct dependencies.