EJBCA up to 6.15.2.5/7.3.1.1 Configuration authorization

Summaryinfo

A vulnerability classified as critical has been found in EJBCA up to 6.15.2.5/7.3.1.1. This impacts an unknown function of the component Configuration Handler. Performing a manipulation results in authorization. This vulnerability is known as CVE-2020-11628. Remote exploitation of the attack is possible. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in EJBCA up to 6.15.2.5/7.3.1.1. This affects some unknown processing of the component Configuration Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in EJBCA before 6.15.2.6 and 7.x before 7.3.1.2. It is intended to support restriction of available remote protocols (CMP, ACME, REST, etc.) through the system configuration. These restrictions can be bypassed by modifying the URI string from a client. (EJBCA's internal access control restrictions are still in place, and each respective protocol must be configured to allow for enrollment.)

The weakness was published 04/08/2020. This vulnerability is uniquely identified as CVE-2020-11628 since 04/07/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 6.15.2.6 or 7.3.1.2 eliminates this vulnerability.

Similar entries are available at VDB-152868, VDB-152867, VDB-152866 and VDB-152864. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• EJBCA

Version

• 6.15.2.0
• 6.15.2.1
• 6.15.2.2
• 6.15.2.3
• 6.15.2.4
• 6.15.2.5
• 7.3.1.0
• 7.3.1.1

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion