Client connections using default TLS certificates from OpenEdge may bypass TLS host name validation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Progress | OpenEdge | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
Vendor Solution
Use the 12.8.0 or above LTS release where the vulnerability does not exist
Vendor Workaround
Replace all use of default OpenEdge TLS certificates with a CA-signed certificate from a recognized certificate authority that contains the necessary information to support host name validation
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-48284 | Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection. This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security. The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.162% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-287 | |
| CPEs | cpe:2.3:a:progress:openedge:*:*:*:*:lts:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Progress
Progress openedge |
|
| CPEs | cpe:2.3:a:progress:openedge:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Progress
Progress openedge |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection. This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security. The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation. | |
| Title | Client connections using default TLS certificates from OpenEdge may bypass TLS host name validation | |
| Weaknesses | CWE-297 | |
| References |
| |
| Metrics |
cvssV3_1
|