CVE-2024-1021 is a medium severity server-side request forgery flaw, scored 6.3, in Rebuild up to 3.5.5. The public record names no fixed version. Restrict network access to the product, check your installed version against the one named in the record, and watch the vendor or project page for a patch.
What's affected
Affected: Rebuild (Ruifang Tech) up to 3.5.5. The record's CVSS 3.1 score is 6.3 (medium), with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. The record names the readRawText function in the HTTP request handler and its url argument. The weakness is filed as CWE-918.
Fixed version: The record names no fixed version. No patched release is confirmed, so check the vendor or project page.
The record's kev flag is false, so this CVE is not in the CISA Known Exploited Vulnerabilities catalog. One thing to note: the VulDB wording in the description calls the issue critical, while the CVSS score in the record is 6.3, which is medium. Treat the numeric score and your own exposure as the guide, and know that both labels exist.
How to check if you're exposed
- Find the product in your inventory and confirm the version. Many of these small applications are installed from a source archive, so the version may live in a file or a database table and not in a package manager.
- Check which networks can reach the application, and whether it is exposed to the internet.
- Review outbound connections from the application host for unexpected internal destinations. Check egress filtering, and confirm that cloud metadata services are not reachable without extra protection.
- Check the vendor or project page for a release newer than the affected one.
What to do now
- Take the product off the internet if it is exposed. Put it behind a VPN or an allow list of known addresses.
- Restrict access at the network layer to the people and systems that need it.
- Watch the vendor or project page for a fixed release, and apply it when one appears. The record does not confirm any patch, so check the source directly.
- Review logs for the signs above and rotate administrator credentials if you see anything unusual.
- Add the product to your inventory and monitoring so a future fix or advisory reaches you. A free in-browser dependency scan covers the third party packages in software you build, though it does not inspect device firmware.
Why it matters
Server-side request forgery lets a user make the server issue requests to addresses of the user's choosing. The server sits inside the network perimeter, so it can reach internal services, admin consoles and cloud metadata addresses that the outsider cannot.
The vector needs a low privilege login and shows limited impact on each of confidentiality, integrity and availability. In cloud deployments the real risk depends on what the server can reach, so network egress rules matter as much as the patch.
Smaller commercial and sample code projects often have no security contact and no release cadence. If no fix arrives, the choices are to harden around the product or to replace it.
The record states that the exploit has been disclosed to the public. That means details are available to others, not that attacks have been observed. Only CISA KEV or a vendor advisory can say that, and neither does here.
Try it yourself
See how an API scan looks at request handling.
Click through it at your own pace, or open it full screen.
Quick check
Is this CVE exploited in the wild?
The record's kev flag is false, so it is not in the CISA Known Exploited Vulnerabilities catalog, and no source I read reports active exploitation. The record does say a public exploit exists. That is a reason to patch or contain it soon, not a report of attacks.
What if there is no patch?
Reduce exposure. Remove internet access, restrict the network, apply the log and credential checks above, and plan to replace the product if it holds sensitive data.
Sources
- Safeguard Gold entry for CVE-2024-1021, built from the NVD record
- NVD record fields: description, CVSS 3.1 vector, CWE list and CPE product data. I did not fetch the researcher write ups listed in the record, so the details above are limited to what the record states.
Last reviewed: 19 October 2026.
