How severe is CVE-2023-32563?

CVE-2023-32563 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-32563?

Affected package information for CVE-2023-32563 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2023-32563?

No fixed version has been published for CVE-2023-32563 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2023-32563 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-32563 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-32563?

CVE-2023-32563 has an EPSS (Exploit Prediction Scoring System) score of 93.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2023-32563?

CVE-2023-32563 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2023-32563?

CVE-2023-32563 affects ivanti avalanche. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2023-32563?

A Nuclei detection template exists for CVE-2023-32563, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-32563 published, and has it been updated?

CVE-2023-32563 was published on August 10, 2023 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2023-32563

CRITICAL

An unauthenticated attacker could achieve the code execution through a RemoteControl server.

Published

Aug 10, 2023

Updated

Nov 21, 2024

Affected

0 pkgs

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

93.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

An unauthenticated attacker could achieve the code execution through a RemoteControl server.

Affected Products

1 product · 1 configurations

Application

avalancheivanti

< 6.4.1

range

Frequently Asked Questions

An unauthenticated attacker could achieve the code execution through a RemoteControl server.

O3 Security · Impact-Aware SCA

Is CVE-2023-32563 in your stack?

O3 detects CVE-2023-32563 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works