CVE-2023-38028
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 insufficient authentication. An unauthenticated remote attacker can exploit this vulnerability to bypass authentication to read system information and operate user's data, but can’t control system or disrupt service.
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 confidenceThis is an authentication bypass vulnerability in Saho attendance devices ADM100 and ADM100FP. An unauthenticated remote attacker can exploit insufficient authentication mechanisms to bypass login and gain unauthorized access to system information and user data, though they cannot gain full system control or disrupt service.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Saho attendance devices on your networkScan your network for devices with vendor identification matching 'Saho' or product models 'ADM100' or 'ADM100FP'. Check network scans, asset inventories, or physically inspect device labels.Affected if Devices are identified as Saho ADM100 or ADM100FP attendance terminals
-
Check the firmware version on the deviceAccess the device administration interface or check the device system information page to retrieve the firmware version number. This is typically found under Settings, System Info, or About sections.Affected if The firmware version matches any of these: 0.0.4.0, 0.0.4.3, 0.0.4.6, 0.0.4.8, q20100602, t190, t17041702, t18051803
-
Verify network exposure of the deviceCheck firewall rules, access control lists, or network segmentation configurations to determine if the device management interface is accessible from untrusted networks or the internet.Affected if The device admin interface is reachable from untrusted networks without VPN or additional authentication layers
-
Test authentication behaviorAttempt to access protected endpoints or system information pages on the device without providing credentials. Observe whether the device grants access without redirecting to a login page.Affected if The device returns system information or allows access to protected features without authentication credentials
You are affected if you have a Saho ADM100 or ADM100FP device running any of the listed firmware versions, especially if it is network-accessible to untrusted attackers.
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 or patches to address the authentication bypass vulnerability, and implement network segmentation to limit exposure of these devices to untrusted networks.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38028 — 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-38028 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