CVE-2022-1070
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 confidenceAethon TUG Home Base Server versions prior to version 24 contains an information disclosure vulnerability where an unauthenticated attacker can freely access hashed user credentials stored on the server.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Aethon TUG Home Base Server is installedLocate the TUG Home Base Server installation directory or check running services for 'TUG' or 'Home Base' processesAffected if The software is present on the system
-
Identify the installed versionCheck the application's about page, installation directory for a version file, or query the running service for its version informationAffected if The version number is less than 24 (e.g., 23.x, 22.x, etc.)
-
Verify the web service is accessibleAttempt to reach the TUG Home Base Server web interface via HTTP/HTTPS from the server itself or a trusted network locationAffected if The web interface responds to requests
-
Check for credential storage exposureInspect the application's data directory for files containing user credential hashes (common patterns: user credentials, password hashes, or database files storing authentication data)Affected if Credential hash files exist and are readable without authentication
You are affected if Aethon TUG Home Base Server version 24 or later is NOT installed and the server's credential storage 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.
dbcve · scoped24
Upgrade Aethon TUG Home Base Server to version 24 or later to remediate this vulnerability.
TUG Home Base Server version 24
- 1. Back up the current TUG Home Base Server configuration and database
- 2. Download TUG Home Base Server version 24 or later from the official Aethon support portal
- 3. Stop the TUG Home Base Server service
- 4. Install version 24 of the TUG Home Base Server
- 5. Verify the installation completed successfully
- 6. Restart the TUG Home Base Server service
- 7. Confirm the vulnerability is remediated by verifying unauthorized access to user credentials is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1070 — 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-1070 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