Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

With 4.0.0 all our internal projects are detected as Jenkins #1596

Closed
TobiX opened this issue Nov 29, 2018 · 3 comments
Closed

With 4.0.0 all our internal projects are detected as Jenkins #1596

TobiX opened this issue Nov 29, 2018 · 3 comments

Comments

@TobiX
Copy link
Contributor

TobiX commented Nov 29, 2018

I'm not really sure why this is suddenly an issue. All our internal artifacts have this in their MANIFEST.MF:

Implementation-URL: http://internal-jenkins.company.com/sites/groupId/artifactId/

When switching from DependencyCheck 3.3.4 to 4.0.0, all those modules are suddenly detected as cpe:/a:jenkins:jenkins.

Some projects have this in their MANIFEST.MF:

X-CI-Job-Name: group/project/release

Those are additionally detected as cpe:/a:jenkins:release...

When I look at the diff between those versions the only culprit can be the lucene update, right?

I know I can work around this issue with local suppressions, but I wonder if there is a different tweakable which would avoid these kinds of false-positives...

@Feralus
Copy link

Feralus commented Nov 30, 2018

Lot of people have this problem. As you already said it is caused by the upgrade from 3.3.4 to 4.0.0.
It looks like it's enough if version matches.

See other Issues: 1580, 1579

@TobiX
Copy link
Contributor Author

TobiX commented Dec 10, 2018

Since this is already discussed in #1580, I'll close this issue.

@TobiX TobiX closed this as completed Dec 10, 2018
@lock
Copy link

lock bot commented Jan 9, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Jan 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants