CVE-2022-27494
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 · uneditedAethon TUG Home Base Server versions prior to version 24 are affected by un unauthenticated attacker who can freely access hashed user credentials.
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 Aethon TUG Home Base Server versions prior to 24 contains an information disclosure vulnerability where unauthenticated attackers can freely access hashed user credentials stored on the server, likely through an unprotected endpoint or file.
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< 24CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Aethon TUG Home Base Server installationLocate the Aethon TUG Home Base Server in your environment. Check for the application running on its typical service port or as a installed service. Confirm the product name matches 'Aethon TUG Home Base Server'.Affected if The server software is present in your environment
-
Determine installed versionAccess the server's admin interface, check the service information, or review installation documentation to find the current version number. Compare this version against the affected range (versions prior to 24).Affected if The installed version is less than 24 (e.g., 23.x, 22.x, etc.)
-
Assess network accessibilityDetermine if the Home Base Server is accessible over the network. Check firewall rules, NAT configurations, and ACLs to see if the server's management interface or API endpoints are reachable from untrusted networks or the internet.Affected if The server is directly accessible from untrusted networks, especially the internet
-
Test for unauthenticated credential accessAttempt to access common endpoint paths or files that might expose user data without authentication. Since the vulnerability involves unauthenticated access to hashed credentials, look for endpoints that return user account information without requiring login credentials.Affected if Unauthenticated access to credential data or user endpoint is possible
You are affected if the Aethon TUG Home Base Server is version 24 or earlier AND the server or its endpoints are accessible over the network 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 data24
Upgrade to version 24 or later to receive the security fix. Until then, apply network segmentation and restrict external access to the server to reduce exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27494 — 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-2022-27494 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