CVE-2022-1059
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 · moderate confidenceThe Aethon TUG Home Base Server versions prior to v24 contain an authentication bypass that allows unauthenticated attackers to access stored hashed user credentials. This information disclosure vulnerability could enable credential cracking or unauthorized access if the hashes are weak or reused elsewhere.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 TUG Home Base Server in your environment - this is typically deployed as a physical or virtual server on premises. Check your asset inventory or scan the network for this specific application.Affected if The product is not present in your environment (not affected)
-
Determine installed versionAccess the server directly or check the application management interface to find the current software version. Compare the version number to the affected range (versions prior to v24).Affected if The installed version is any version before v24 (v23, v22, etc.)
-
Check network accessibilityVerify if the TUG Home Base Server is exposed to network access from untrusted networks. Attempt to access the server from an external network perspective or review firewall rules.Affected if The server is accessible from untrusted networks without proper segmentation
-
Assess authentication controlsReview the server's authentication configuration and attempt to determine if the credential storage mechanism is accessible without valid credentials. Check for exposed API endpoints or administrative interfaces.Affected if The server allows unauthenticated access to user credential data or administrative functions
You are affected if Aethon TUG Home Base Server is running and the installed version is before v24, especially if the server is network-accessible.
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.
dbcve · scoped24
Upgrade the TUG Home Base Server to version 24 or later. If immediate patching is not possible, restrict network access to the server and monitor for unauthorized access attempts.
TUG Home Base Server version 24
- Upgrade Aethon TUG Home Base Server to version 24 or later to remediate the vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1059 — 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-1059 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