CVE-2024-0418 is a medium severity denial of service vulnerability in upRedSun File Sharing Wizard up to 1.5.0, scored CVSS 5.3. It affects the GET request handler through the web server component. The record names no fixed version, so check the vendor or project and restrict access.
What's affected
The record names upRedSun File Sharing Wizard, up to 1.5.0. The weakness is resource consumption leading to denial of service: the program can be made to stop serving requests. The weakness is tracked as CWE-404. The affected code is the GET request handler, reached through the web server component. The record says the issue can be reached remotely and that an exploit has been disclosed publicly. It was published on 2024-01-11 and the VulDB identifier is 250438.
The researcher's public post on cxsecurity says File Sharing Wizard 1.5.0 was tested on Windows XP Professional Service Pack 2 and 3, that the server does not properly handle a request with a large amount of data sent with the GET method, and that the vendor was not notified. That post is the only detail beyond the record that we could read.
The record does not name a fixed version. Treat the product as unpatched until the vendor or project says otherwise. It is not on the CISA Known Exploited Vulnerabilities list, and the sources we read do not report exploitation.
How to check if you're exposed
Find out whether the software runs anywhere you manage. It is old Windows software, so check desktops, lab machines and forgotten servers. Look for the program in the installed software list, and for a listening web service on the machine:
netstat -ano | findstr LISTENING
Match the listening ports to the process. If the program is exposed to a network you do not control, treat it as at risk.
Look at how often the service stops without explanation. A crash with large requests in the access log, if any is kept, fits the description in the record. There is no vendor guidance to check against.
A dependency scanner will not find a standalone application like this on its own, because it is deployed code, not a package. You can still use Safeguard's free in-browser dependency scan at gold.safeguard.sh/scan on any project that bundles it as a library, and the Gold entry for CVE-2024-0418 tracks the record as it changes.
What to do now
- Find out whether File Sharing Wizard runs on any machine you manage.
- Remove it from machines that do not need it, or from any network you do not control.
- Keep it off the internet. Put it behind a firewall or VPN if it must run.
- Look for a maintained replacement, since the sources we read show no fix and the researcher's post says the vendor was not notified.
- Monitor the service so a crash is noticed and restarted, and consider a supervisor that limits request size.
- Plan to retire the software, as an unmaintained server on a legacy operating system is a standing risk.
Why it matters
This is an availability flaw. A request the server cannot handle properly makes it stop. For a small file or web server on an old operating system, the effect is that the service goes down until someone restarts it.
The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, scored 5.3 (medium), with no effect on confidentiality or integrity. VulDB's wording calls it problematic. Public exploit code exists for this class of issue, according to the description, so an exposed copy can be knocked over by anyone who looks.
This record is not on the CISA Known Exploited Vulnerabilities list. The description does say the exploit has been disclosed to the public and may be used, which means the technical detail is available to anyone who looks. That is a reason to act on exposed copies even though no exploitation is recorded in the sources we could read.
Quick check
Is CVE-2024-0418 known to be exploited in the wild?
It is not on the CISA Known Exploited Vulnerabilities list and the sources we could read do not report exploitation. The description says a public exploit exists, so do not wait for confirmation.
Is there a fixed version of File Sharing Wizard?
The record does not name one. Check the vendor or project, and if none exists, restrict access or retire the software.
Sources
- Gold entry for CVE-2024-0418
- NVD record for CVE-2024-0418, including VulDB entry 250438, as summarized in the Safeguard record file. The cxsecurity post by the researcher was read.
Last reviewed: 19 October 2026.
