Skip to content

Unexpected error SSLPeerUnverifiedException when upgrading from 12.1.0 to 12.1.1 #7632

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

Open
irineu-rassytem opened this issue May 6, 2025 · 1 comment · Fixed by #7617
Open
Labels
Milestone

Comments

@irineu-rassytem
Copy link

Hello,

I'm using an NVD cache hosted on AWS S3, for this we use vulnz and we are currently on version vulnz-8.1.1.jar and we are using dependency-check-maven version 12.1.0
With this combination everything is working perfectly.

Today, I tried to update dependency-check-maven to version 12.1.1 and when I did that, our build stopped working and started spitting out the following error:

[ERROR] UpdateException: Unable to download the data feed META files
[ERROR] caused by DownloadFailedException: Download failed, error downloading 'https://s3.amazonaws.com/xxxxxxxxxx/cache.properties'; Certificate for <s3.amazonaws.com> doesn't match any of the subject alternative names: [s3.amazonaws.com, *.s3.amazonaws.com, *.s3.dualstack.us-east-1.amazonaws.com, s3.dualstack.us-east-1.amazonaws.com, *.s3.us-east-1.amazonaws.com, s3.us-east-1.amazonaws.com, *.s3-control.us-east-1.amazonaws.com, s3-control.us-east-1.amazonaws.com, *.s3-control.dualstack.us-east-1.amazonaws.com, s3-control.dualstack.us-east-1.amazonaws.com, *.s3-accesspoint.us-east-1.amazonaws.com, *.s3-accesspoint.dualstack.us-east-1.amazonaws.com, *.s3-deprecated.us-east-1.amazonaws.com, s3-deprecated.us-east-1.amazonaws.com, s3-external-1.amazonaws.com, *.s3-external-1.amazonaws.com, s3-external-2.amazonaws.com, *.s3-external-2.amazonaws.com]
[ERROR] caused by SSLPeerUnverifiedException: Certificate for <s3.amazonaws.com> doesn't match any of the subject alternative names: [s3.amazonaws.com, *.s3.amazonaws.com, *.s3.dualstack.us-east-1.amazonaws.com, s3.dualstack.us-east-1.amazonaws.com, *.s3.us-east-1.amazonaws.com, s3.us-east-1.amazonaws.com, *.s3-control.us-east-1.amazonaws.com, s3-control.us-east-1.amazonaws.com, *.s3-control.dualstack.us-east-1.amazonaws.com, s3-control.dualstack.us-east-1.amazonaws.com, *.s3-accesspoint.us-east-1.amazonaws.com, *.s3-accesspoint.dualstack.us-east-1.amazonaws.com, *.s3-deprecated.us-east-1.amazonaws.com, s3-deprecated.us-east-1.amazonaws.com, s3-external-1.amazonaws.com, *.s3-external-1.amazonaws.com, s3-external-2.amazonaws.com, *.s3-external-2.amazonaws.com]
[ERROR] NoDataException: No documents exist

If I go back to version 12.1.0, everything works again.

How can I solve this problem?
Is there a bug in version 12.1.1?

@aikebah
Copy link
Collaborator

aikebah commented May 7, 2025

That would be https://issues.apache.org/jira/browse/HTTPCLIENT-2365, maybe best to stay at 12.1.0 for now in your case.

Next release of DependencyCheck should resolve it by way of an Apache HTTPClient library version update.

As an alternative you could try and see if forcing httpclient5 to version 5.4.4 by explicitly adding it as a plugin dependency would make it work for you with 12.1.1

<plugin>
    <groupId>org.owasp</groupId>
    <artifactId>dependency-check-maven</artifactId>
    ...
    <dependencies>
        <dependency>
            <groupId>org.apache.httpcomponents.client5</groupId>
            <artifactId>httpclient5</artifactId>
            <version>5.4.4</version>
        </dependency>                    
    </dependencies>
</plugin>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants