CVE-2024-38467
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 · uneditedShenzhen Guoxin Synthesis image system before 8.3.0 allows unauthorized user information retrieval via the queryUser API.
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 · high confidenceThe Shenzhen Guoxin Synthesis image system before version 8.3.0 contains an unauthenticated information disclosure vulnerability in the queryUser API. Attackers can exploit this API endpoint to retrieve user information without any authentication or authorization, exposing sensitive user data such as usernames, emails, or other account details.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.3.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify Guoxinled Synthesis Image System installationLocate the Guoxinled Synthesis Image System application in your environment. Check installed programs on Windows (Add/Remove Programs), Linux package managers, or scan network for the service. Look for services running on common web ports (80, 443, 8080) that may be this application.Affected if The system has Guoxinled Synthesis Image System installed and running.
-
Determine installed versionCheck the installed version of Guoxinled Synthesis Image System. This may be visible in the application itself, in installation files, or via an API endpoint that returns version information. Compare your version number to the affected range of versions before 8.3.0.Affected if The installed version is lower than 8.3.0.
-
Locate the queryUser API endpointIdentify if the queryUser API endpoint is accessible in your deployment. This is typically found at a path similar to /api/queryUser, /queryUser, or similar variations. Check your web server logs or API documentation for this endpoint.Affected if The queryUser API endpoint exists and is routable in your environment.
-
Test unauthenticated access to queryUser APISend an HTTP request to the queryUser endpoint without providing any authentication credentials (no API key, no session token, no login). For example: curl -X GET http://TARGET_IP:PORT/queryUser or similar path. Observe if the request succeeds and returns user data.Affected if The queryUser API responds with user information without requiring any authentication.
Your environment is affected if Guoxinled Synthesis Image System versions below 8.3.0 are installed and the queryUser API endpoint is accessible without authentication credentials.
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 data8.3.0
Upgrade to version 8.3.0 or later which includes proper authentication for the queryUser API. If immediate upgrade is not possible, implement authentication and authorization controls on the queryUser API endpoint to restrict access to authenticated users only.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38467 — 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-38467 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