[
https://issues.apache.org/jira/browse/SYNCOPE-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570199#comment-16570199
]
Massimiliano Perrone commented on SYNCOPE-1349:
-----------------------------------------------
Hi [~ABakerIII],
I don't know which kind of Open Source projects have you analyzed in the past
with your tool and, sincerely, I can have good dreams also without this
information.
Coming to your comments... you are talking about lucky, precisely *exceedily
lucky.* A question for you. Do you think that the dependencies choice for an
Open Source (or not) project is a lottery? Especially for a security middleware
as usually Syncope is used?
Something like:
"I need a dependency but, which one? Ah, this one seems to be nice hopefully
all go well! (finger crossed, image the emoticon ;))."
Second thing from your words: *99.999% of projects are no so lucky.* Another
time lucky... Oh well... anyway, 99.99% are you sure?
So only Syncope is vulnerability free? Or there is at least one project without
security issue? We are the only *lucky* guys in the open source world?
I don't know if [~ilgrosso] will choice to use your tool, he is the boss.
Personally I'm not agree because of your bad presentation.
Anyway, after your comments today I'm feeling lucky; so it's the right day to
buy a scratch card and, of course, choise the right library!
Have a good day Albert and good luck :)
> 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)
