Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2024-7346

Client connections using default TLS certificates from OpenEdge may bypass TLS host name validation

High7.2EPSS 0.16%
Published
Updated
Reserved
Assigned by
ProgressSoftware

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.

Scores

CVSS scores of CVE-2024-7346, by who scored it
Scored byCVSSScoreVector
ProgressSoftwareCNA (assigner)3.1High7.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
NVDNVD · Analyzed3.1Medium4.8CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.2.

Weakness

Affected products

  • Progress · OpenEdge

    • affected 11.7.0 – ≤ 11.7.19
    • affected 12.2.0 – ≤ 12.2.14
    • unaffected 12.8.0

What to do

Solution: Use the 12.8.0 or above LTS release where the vulnerability does not exist

Solution: Use the 12.2 LTS release at the 12.2.15 Update level or above

Solution: Use the 11.7 LTS release at the 11.7.20 Update level or above

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

Workaround: Use the "nohostverify" switch in development environments when clients need to bypass host name validation as a convenience prior to establishing valid certificates for production.

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-7346 badge
[![CVE-2024-7346](https://trackcve.app/badge/CVE-2024-7346.svg)](https://trackcve.app/cve/CVE-2024-7346)

Record last updated .