How severe is CVE-2020-4367?

CVE-2020-4367 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2020-4367 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-4367?

CVE-2020-4367 affects Ibm Planning Analytics Local. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-4367?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-4367 published?

CVE-2020-4367 was published on 2020-06-02 and last updated on 2026-06-17.

CVE-2020-4367

CVE-2020-4367 is a high-severity vulnerability in Ibm Planning Analytics Local with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (52nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-327
Affected product: Ibm Planning Analytics Local
Published: 2020-06-02
Last modified: 2026-06-17

Description

IBM Planning Analytics Local 2.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 179001.

Frequently asked questions

What is CVE-2020-4367?: IBM Planning Analytics Local 2.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 179001.
How severe is CVE-2020-4367?: CVE-2020-4367 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2020-4367 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-4367?: CVE-2020-4367 affects Ibm Planning Analytics Local. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-4367?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-4367 published?: CVE-2020-4367 was published on 2020-06-02 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:ibm:planning_analytics_local:*:*:*:*:*:*:*:*

More vulnerabilities in Ibm Planning Analytics Local

CVE-2020-4670 — Critical (CVSS 9.1): IBM Planning Analytics Local 2.0 connects to a Redis server. The Redis server, an in-memory data structure store,…
CVE-2020-4669 — Critical (CVSS 9.1): IBM Planning Analytics Local 2.0 connects to a MongoDB server. MongoDB, a document-oriented database system, is…
CVE-2025-36357 — High (CVSS 8.0): IBM Planning Analytics Local 2.1.0 through 2.1.14 could allow a remote authenticated user to traverse directories on…
CVE-2020-4985 — High (CVSS 7.5): IBM Planning Analytics Local 2.0 could allow an attacker to obtain sensitive information due to accepting body…
CVE-2024-35143 — Medium (CVSS 6.7): IBM Planning Analytics Local 2.0 and 2.1 connects to a MongoDB server. MongoDB, a document-oriented database system, is…
CVE-2026-1267 — Medium (CVSS 6.5): IBM Planning Analytics Local 2.1.0 through 2.1.17 could allow an unauthorized access to sensitive application data and…

All CVEs affecting Ibm Planning Analytics Local →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →