How severe is CVE-2023-32549?

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

Is CVE-2023-32549 being actively exploited?

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

What products are affected by CVE-2023-32549?

CVE-2023-32549 affects Canonical Landscape. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2023-32549?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2023-32549 published?

CVE-2023-32549 was published on 2023-06-06 and last updated on 2026-06-17.

CVE-2023-32549

CVE-2023-32549 is a medium-severity vulnerability in Canonical Landscape with a CVSS 3.x base score of 6.8. 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-338.

Key facts

Severity: Medium (CVSS 3.x base score 6.8)
EPSS exploit prediction: 1% (42nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-338
Affected product: Canonical Landscape
Published: 2023-06-06
Last modified: 2026-06-17

Description

Landscape cryptographic keys were insecurely generated with a weak pseudo-random generator.

Frequently asked questions

What is CVE-2023-32549?: Landscape cryptographic keys were insecurely generated with a weak pseudo-random generator.
How severe is CVE-2023-32549?: CVE-2023-32549 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2023-32549 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (42nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-32549?: CVE-2023-32549 affects Canonical Landscape. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-32549?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2023-32549 published?: CVE-2023-32549 was published on 2023-06-06 and last updated on 2026-06-17.

References

https://bugs.launchpad.net/landscape/+bug/1929034

Affected products (1)

cpe:2.3:a:canonical:landscape:*:*:*:*:*:*:*:*

More vulnerabilities in Canonical Landscape

CVE-2023-32550 — Critical (CVSS 9.3): Landscape's server-status page exposed sensitive system information. This data leak included GET requests which contain…
CVE-2023-32551 — Medium (CVSS 6.1): Landscape allowed URLs which caused open redirection.

All CVEs affecting Canonical Landscape →

Other CWE-338 vulnerabilities

CVE-2026-56141 — Critical (CVSS 9.8): In JetBrains Hub before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 account…
CVE-2026-3256 — Critical (CVSS 9.8): HTTP::Session versions before 0.54 for Perl defaults to using insecurely generated session ids. HTTP::Session defaults…
CVE-2025-15604 — Critical (CVSS 9.8): Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions. In versions…
CVE-2025-40926 — Critical (CVSS 9.8): Plack::Middleware::Session::Simple versions before 0.05 for Perl generates session ids insecurely. The default session…
CVE-2026-2439 — Critical (CVSS 9.8): Concierge::Sessions versions from 0.8.1 before 0.8.5 for Perl generate insecure session ids. The generate_session_id…
CVE-2025-15578 — Critical (CVSS 9.8): Maypole versions from 2.10 through 2.13 for Perl generates session ids insecurely. The session id is seeded with the…

Browse all CWE-338 vulnerabilities →