CVE-2023-38030
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 · uneditedSaho’s attendance devices ADM100 and ADM-100FP have a vulnerability of missing authentication for critical functions. An unauthenticated remote attacker can execute system commands in partial website URLs to read sensitive device information without permissions.
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 confidenceSaho ADM100 and ADM-100FP attendance devices contain a missing authentication vulnerability in their web interface. Attackers can execute system commands through partial URL paths without any credentials, allowing unauthorized access to sensitive device information including potentially user data, logs, and system configuration.
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= 0.0.4.0= 0.0.4.3= 0.0.4.6= 0.0.4.8= q20100602= t190= t17041702= t18051803= q20100602= t190= t17041702= t18051803CVSS 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 the device modelLocate the physical device or access the device's web interface to confirm it is a Saho ADM100 or ADM-100FP attendance device. Check device labeling, documentation, or login page for the model name.Affected if The device is a Saho ADM100 or ADM-100FP model.
-
Determine the firmware versionAccess the device's web interface or administrative console to find the firmware version. This is typically shown in system information, settings, or an about page. Compare the installed version against the affected list: ADM100 versions 0.0.4.0, 0.0.4.3, 0.0.4.6, 0.0.4.8, q20100602, t190, t17041702, t18051803; ADM100FP versions q20100602, t190, t17041702, t18051803.Affected if The installed firmware version matches one of the versions listed in the affected products.
-
Verify web interface accessibilityAttempt to access the device web interface over the network using HTTP/HTTPS. Try accessing partial URL paths or common administrative endpoints without providing any login credentials.Affected if The web interface is reachable and allows access to any functionality or information without requiring authentication.
The device is affected if it is a Saho ADM100 or ADM-100FP with a firmware version matching one of the listed affected versions and the web interface is accessible without authentication.
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 dataApply vendor firmware updates when available, or restrict network access to these devices using firewall rules to prevent unauthenticated external access to the web management interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38030 — 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-2023-38030 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