CVE-2022-34006
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 · uneditedAn issue was discovered in TitanFTP (aka Titan FTP) NextGen before 1.2.1050. When installing, Microsoft SQL Express 2019 installs by default with an SQL instance running as SYSTEM with BUILTIN\Users as sysadmin, thus enabling unprivileged Windows users to execute commands locally as NT AUTHORITY\SYSTEM, aka NX-I674 (sub-issue 2). NOTE: as of 2022-06-21, the 1.2.1050 release corrects this vulnerability in a new installation, but not in an upgrade installation.
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 confidenceTitanFTP NextGen before 1.2.1050 installs Microsoft SQL Express 2019 with insecure defaults—the SQL service runs as NT AUTHORITY\SYSTEM and the BUILTIN\Users group is granted sysadmin privileges. This allows any local Windows user to connect to the SQL instance with sysadmin rights and execute operating system commands as the SYSTEM account, achieving local privilege escalation.
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< 1.2.1050CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Identify TitanFTP NextGen installation and versionCheck the installed version of TitanFTP NextGen by examining the application in Windows Programs and Features, or check the installation directory for version information. Compare against the affected range: versions before 1.2.1050 are vulnerable.Affected if TitanFTP NextGen is installed with a version lower than 1.2.1050.
-
Verify SQL Express 2019 installationCheck if Microsoft SQL Express 2019 is installed on the system. This may appear as 'SQL Server 2019 Express' in Windows Programs and Features. The installation is typically performed by the TitanFTP NextGen installer.Affected if SQL Express 2019 was installed as part of the TitanFTP NextGen installation.
-
Examine the SQL Server service accountOpen Windows Services, locate the SQL Server service (named something like 'SQL Server (SQLEXPRESS)'), and check the Log On As property. This can also be checked via the command: sc qc mssql$sqlexpressAffected if The SQL service runs as NT AUTHORITY\SYSTEM.
-
Check sysadmin role membership for BUILTIN\UsersConnect to the SQL Express instance (using sqlcmd or SQL Server Management Studio Express) and run: SELECT member.name AS MemberName FROM sys.server_rolemembers rm JOIN sys.server_principals role ON rm.role_principal_id = role.principal_id JOIN sys.server_principals member ON rm.member_principal_id = member.principal_id WHERE role.name = 'sysadmin'. Alternatively, check via: EXEC sp_helpsrvrolemember 'sysadmin'.Affected if BUILTIN\Users appears as a member of the sysadmin server role.
A system is affected if TitanFTP NextGen version is below 1.2.1050 AND SQL Express 2019 was installed with SYSTEM-level service account AND BUILTIN\Users has sysadmin privileges, allowing any local user to execute commands as SYSTEM.
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 · scoped1.2.1050
Upgrade to version 1.2.1050 or later for new installations. For existing/upgrade installations, manually reconfigure SQL Express by changing the service account from SYSTEM to a low-privilege service account and removing BUILTIN\Users from the sysadmin server role.
1.2.1050 (note: vendor states this corrects the vulnerability in new installation only, not upgrade installations)
- Verify the current SQL Express service account and remove BUILTIN\Users from sysadmin role using SQL Server Management Studio or command line: `sqlcmd -E -Q "EXEC sp_dropsrvrolemember 'BUILTIN\Users', 'sysadmin'"`
- Change the SQL Express service to run under a dedicated low-privilege Windows service account instead of SYSTEM
- If SQL service account change is not possible, at minimum remove BUILTIN\Users from the sysadmin server role on the SQL instance
- Restart the SQL Express service after making changes
- For new installations, upgrade to version 1.2.1050 which addresses this issue in fresh installs per vendor notes
- After any configuration changes, verify unprivileged users can no longer escalate privileges via SQL server roles
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34006 — 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-34006 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