[
https://issues.apache.org/jira/browse/SYNCOPE-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570278#comment-16570278
]
Albert Baker commented on SYNCOPE-1349:
---------------------------------------
Masi :
I have generally looked at large projects. std components/systems that every sw
dev has heard of and are widely used. They /all/ have had yrs old known
vulnerabilities.
I have been writting sw for 30yrs. sw devs go about thier business by haveing
a customer resquested feature, form an idea about how to do it, pick already
known apis, or google for help; to get the feature completed. They usually
end up using the most up2date libraires. They usually dont update the build
every 3-6 months to ensure thay have the latest library. Usually the version
dependencies in a build stay the way they were originally written until
something breaks. This pattern continues for years. For large projects,
there is a large set of dependencies. Over years, any/every large set of
dependecies will accumulate vulnerabilities.
Your teams' dilligence in keeping the versions up2date is exceedingly rare.
GREAT ! for this project and for your skill and high level of care. What will
happen in a year or two or three when you move on, go showhere else, have more
cares that take up your time; and you stop caring for this project ? The
OWASP Check, will hopefully still be there, informing the next guy that there
is a problem.
> Please add OWASP Dependency Check to the build (pom.xml)
> --------------------------------------------------------
>
> Key: SYNCOPE-1349
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1349
> Project: Syncope
> Issue Type: New Feature
> Affects Versions: 2.0.10, 2.1.1, 3.0.0
> Environment: All development, build, test, environments.
> Reporter: Albert Baker
> Priority: Major
> Labels: build, easy-fix, security
> Attachments: dependency-check-report.html
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Please add OWASP Dependency Check to the build (pom.xml). OWASP DC makes an
> outbound REST call to MITRE Common Vulnerabilities & Exposures (CVE) to
> perform a lookup for each dependant .jar to list any/all known
> vulnerabilities for each jar. This step is needed because a manual MITRE CVE
> lookup/check on the main component does not include checking for
> vulnerabilities in components or in dependant libraries.
> OWASP Dependency check :
> https://www.owasp.org/index.php/OWASP_Dependency_Check has plug-ins for most
> Java build/make types (ant, maven, ivy, gradle).
> Also, add the appropriate command to the nightly build to generate a report
> of all known vulnerabilities in any/all third party libraries/dependencies
> that get pulled in. example : mvn -Powasp -Dtest=false -DfailIfNoTests=false
> clean aggregate
> Generating this report nightly/weekly will help inform the project's
> development team if any dependant libraries have a reported known
> vulnerailities. Project teams that keep up with removing vulnerabilities on
> a weekly basis will help protect businesses that rely on these open source
> componets.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
