CVE-2024-5050
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability, which was classified as critical, was found in Wangshen SecGate 3600 up to 20240516. This affects an unknown part of the file /?g=log_import_save. The manipulation of the argument reqfile leads to unrestricted upload. It is possible to initiate the attack remotely. The associated identifier of this vulnerability is VDB-264747.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceUnrestricted file upload vulnerability in Wangshen SecGate 3600 web gateway product. The log_import_save function at /?g=log_import_save allows arbitrary file upload via manipulation of the reqfile parameter, which could enable remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Wangshen SecGate 3600 installationIdentify if Wangshen SecGate 3600 web gateway product is deployed in the environment by reviewing asset inventory, network diagrams, or by accessing the management interface at the known IP/hostnameAffected if Wangshen SecGate 3600 is present in the environment
-
Check installed version against affected releasesAccess the product management interface or system settings to retrieve the installed version number, then compare against any documented affected version rangesAffected if Installed version falls within an affected version range and the product is unpatched
-
Verify management interface network exposureDetermine if the web management interface is accessible from untrusted networks by reviewing firewall rules, ACLs, or performing network connectivity tests from external IPsAffected if The management interface is exposed to the internet or untrusted internal networks
-
Inspect for suspicious uploaded filesExamine web server directories (especially upload and temporary folders) for unexpected files with extensions such as .php, .asp, .jsp, .exe, or .sh that were created around the time of potential exploitationAffected if Unexpected executable or script files exist in web-accessible directories without legitimate business justification
-
Review access logs for log_import_save endpointSearch web server access logs and application logs for requests to /?g=log_import_save, particularly those containing the reqfile parameter with unusual values or file extensionsAffected if Requests to the log_import_save endpoint with reqfile parameter are present in logs, especially from untrusted sources
You are affected if Wangshen SecGate 3600 is deployed, unpatched, and its management interface (containing the vulnerable log_import_save function) is network-accessible, or if evidence of exploitation attempts appears in logs or file system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network access to the management interface; contact Wangshen for official patch; if exploitation is suspected, conduct forensic analysis and rebuild compromised systems.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5050 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5050 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data