commons-httpclient:commons-httpclient@2.0-beta1 vulnerabilities

  • latest version

    20020423

  • first published

    19 years ago

  • latest version published

    19 years ago

  • licenses detected

  • package manager

  • Direct Vulnerabilities

    Known vulnerabilities in the commons-httpclient:commons-httpclient package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Man-in-the-Middle (MitM)

    commons-httpclient:commons-httpclient is a HttpClient component of the Apache HttpComponents project.

    Affected versions of this package are vulnerable to Man-in-the-Middle (MitM) due to not verifing the requesting server's hostname agains existing domain names in the SSL Certificate. The AbstractVerifier does not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via a certificate with a subject that specifies a common name in a field that is not the CN field.

    NOTE: this issue exists because of an incomplete fix for CVE-2012-5783.

    How to fix Man-in-the-Middle (MitM)?

    There is no fixed version for commons-httpclient:commons-httpclient.

    [0,)
    • M
    Improper Certificate Validation

    commons-httpclient:commons-httpclient is a HttpClient component of the Apache HttpComponents project.

    Affected versions of this package are vulnerable to Improper Certificate Validation due to not verifying that the requesting server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate. This allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

    NOTE: This plugin has been deprecated, but a fix has been released in version 3.1-jenkins-3 on a special Jenkins fork of the project.

    How to fix Improper Certificate Validation?

    Upgrade commons-httpclient:commons-httpclient to version 3.1-jenkins-1 or higher.

    [,3.1-jenkins-1)