What is CVE-2020-17514?

CVE-2020-17514 is a vulnerability in Apache Fineract prior to version 1.5.0 that disables HTTPS hostname verification.

What is the severity of CVE-2020-17514?

The severity of CVE-2020-17514 is high with a CVSS score of 7.4.

How does CVE-2020-17514 affect Apache Fineract?

CVE-2020-17514 affects Apache Fineract versions prior to 1.5.0 by disabling the HTTPS hostname verification in the ProcessorHelper's configureClient method.

How can a man in the middle attack be successful due to CVE-2020-17514?

Under typical deployments, a man in the middle attack could be successful because of the disabled HTTPS hostname verification in Apache Fineract prior to version 1.5.0.

How can I fix CVE-2020-17514 in Apache Fineract?

To fix CVE-2020-17514, update Apache Fineract to version 1.5.0 or above, which addresses the vulnerability by enabling HTTPS hostname verification in the ProcessorHelper's configureClient method.

Vulnerability/
CVE-2020-17514

high

7.4

27/5/2021

4/8/2024

CVE-2020-17514: disabled hostname verificiation

First published: Thu May 27 2021(Updated: )

Apache Fineract prior to 1.5.0 disables HTTPS hostname verification in ProcessorHelper in the configureClient method. Under typical deployments, a man in the middle attack could be successful.

Credit: security@apache.org

Affected Software	Affected Version	How to fix
Apache Fineract	<1.5.0

Remedy

https://issues.apache.org/jira/browse/FINERACT-1211

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is CVE-2020-17514?
CVE-2020-17514 is a vulnerability in Apache Fineract prior to version 1.5.0 that disables HTTPS hostname verification.
What is the severity of CVE-2020-17514?
The severity of CVE-2020-17514 is high with a CVSS score of 7.4.
How does CVE-2020-17514 affect Apache Fineract?
CVE-2020-17514 affects Apache Fineract versions prior to 1.5.0 by disabling the HTTPS hostname verification in the ProcessorHelper's configureClient method.
How can a man in the middle attack be successful due to CVE-2020-17514?
Under typical deployments, a man in the middle attack could be successful because of the disabled HTTPS hostname verification in Apache Fineract prior to version 1.5.0.
How can I fix CVE-2020-17514 in Apache Fineract?
To fix CVE-2020-17514, update Apache Fineract to version 1.5.0 or above, which addresses the vulnerability by enabling HTTPS hostname verification in the ProcessorHelper's configureClient method.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/remedy
agent/last-modified-date
agent/severity
agent/title
agent/author
agent/tags
agent/event
agent/description
agent/first-publish-date
vendor/apache
canonical/apache fineract

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.