How to Fix CVE-2024-28988: CWE-502 Deserialization of Untrusted Data in Web Help Desk

What is CVE-2024-28988?

SolarWinds Web Help Desk was found to be susceptible to a Java Deserialization Remote Code Execution vulnerability that, if exploited, would allow an attacker to run commands on the host machine. This vulnerability was found by the ZDI team after researching a previous vulnerability and providing this report. The ZDI team was able to discover an unauthenticated attack during their research.

In short, a successful attacker gets remote code execution on the affected system. No confirmed in-the-wild exploitation is listed in CISA KEV at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

Check whether you run Solarwinds Web Help Desk in your environment, then compare your installed version against the Affected row above.

Open the product's admin UI and check the build version in the About panel.

How to fix CVE-2024-28988

1. Read the official vendor advisory linked at the bottom of this page and identify the exact patched build for your release train.
2. Download the patched build of Web Help Desk from the vendor's support portal. Use only signed images from the vendor.
3. Back up configuration and, where supported, take a snapshot of the host or appliance before you start.
4. Apply the update following the vendor's documented procedure. For clustered or high-availability deployments, patch the standby node first, fail over, then patch the previously active node.
5. Restart the affected service or appliance if the upgrade procedure requires it.
6. Re-run the version check from the previous section and confirm the build matches the fixed release.

Update the Java dependency

# The patched Maven / Gradle version is listed in the vendor advisory: https://support.solarwinds.com/SuccessCenter/s/article/WHD-12-8-3-Hotfix-3
# Maven
mvn versions:set -DnewVersion=<patched-version> -DartifactId=<artifact-id>
mvn clean install

# Gradle
./gradlew --refresh-dependencies build

# Verify the runtime version
java -version

# Vendor advisory: https://support.solarwinds.com/SuccessCenter/s/article/WHD-12-8-3-Hotfix-3
# Restart the affected Windows service after replacing the JAR
Restart-Service -Name "<service-name>"
Get-Service -Name "<service-name>"

Verify the fix landed

# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://support.solarwinds.com/SuccessCenter/s/article/WHD-12-8-3-Hotfix-3
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2024-28988 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you can't patch immediately

If patching has to wait, block external access to the affected service at the firewall and restrict to a small, audited management network. Enable any vendor-recommended detection rules or WAF signatures listed in the advisory. None of these are a substitute for the patch.

How to verify the fix worked

Confirm the running build of Web Help Desk matches the fixed version listed by the vendor. Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2024-28988 has cleared. Where the vendor publishes a detection rule or IOCs, sweep your logs for evidence of pre-patch exploitation.

Why this CVE matters

CVSS 9.8 (Critical) reflects either remote, unauthenticated exploitability, full impact on confidentiality / integrity / availability, or both. Most internal SLAs map a Critical rating to a 7-to-15 day patch deadline regardless of in-the-wild reports. Public-facing instances should be patched on the shorter end of that window.

Monitoring and detection

After you apply the patch, treat the affected component as a known-good baseline and watch for regression. Concrete steps:

• Re-run your usual vulnerability scanner on a weekly cycle for the next month and confirm the finding stays clear.
• Forward the affected component's logs to your SIEM, then write a rule for any failed-auth burst or unusual configuration change on the component.
• If the vendor advisory lists indicators of compromise, hash patterns, or specific log strings, build detection rules in your SIEM around them and back-search the last 90 days of logs.
• Tag the patched build in your CMDB so future audits can confirm it stayed patched through any rebuild or re-image.

Defensive hardening beyond the patch

Patching closes this specific CVE. A few common-sense controls reduce the blast radius of the next one in the same component:

• Restrict network access to the affected component to known administrative networks at the firewall.
• Enable verbose audit logging and forward events to your SIEM for at least 90 days.
• Enforce two-factor authentication on any account that can administer the affected component.
• Run a fresh asset inventory after the patch to confirm no shadow instances were missed.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2024-50623: Unrestricted File Upload in In Cleo Harmony — Unrestricted File Upload in In Cleo Harmony
• How to Fix CVE-2024-7262: Path Traversal in WPS Office — Path Traversal in WPS Office
• How to Fix CVE-2024-0138: CWE-862 Missing Authorization in Base Command Manager , CWE-862 Missing Authorization in Base Command Manager
• How to Fix CVE-2024-28986: SolarWinds Web Help Desk Java Deserialization , SolarWinds Web Help Desk Java Deserialization
• How to Fix CVE-2024-11667: Path Traversal in Zyxel ATP series firmware , Path Traversal in Zyxel ATP series firmware

Is CVE-2024-28988 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That can change, so monitor the advisory and KEV catalog.

How severe is CVE-2024-28988?

CVSS rates it 9.8 (Critical). Treat it accordingly in your prioritisation queue.

Do I have to take Web Help Desk offline to apply the patch?

That depends on your deployment topology. For high-availability or clustered setups you can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

References

• Official vendor advisory: https://support.solarwinds.com/SuccessCenter/s/article/WHD-12-8-3-Hotfix-3
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28988
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• https://www.solarwinds.com/trust-center/security-advisories/CVE-2024-28988

*Written by Sai Kiran Pandrala on 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor's advisory before applying changes in production.*