CVE-2018-12470
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 · uneditedA SQL Injection in the RegistrationSharing module of SUSE Linux SMT allows remote attackers to cause execute arbitrary SQL statements. Affected releases are SUSE Linux SMT: versions prior to 3.0.37.
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 confidenceA SQL Injection vulnerability exists in the RegistrationSharing module of SUSE Linux SMT. Remote attackers can execute arbitrary SQL statements through unsanitized input in this module, potentially compromising the entire database and system.
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< 3.0.37CVSS 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
- High
CVSS:3.0/AV:N/AC:L/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.
-
Check installed SUSE SMT versionRun 'rpm -q smt' or 'smt --version' to retrieve the installed SUSE Subscription Management Tool package versionAffected if The version number returned is less than 3.0.37 (e.g., 3.0.36, 3.0.35, etc.)
-
Verify RegistrationSharing module presenceCheck if the RegistrationSharing module is installed by looking for 'RegistrationSharing' in the output of 'rpm -qa | grep -i smt' or by listing available SMT modules via 'smt list-modules'Affected if RegistrationSharing module is found and SMT version is below 3.0.37
-
Inspect SMT configuration for RegistrationSharingExamine /etc/smt.conf or the SMT database configuration for references to RegistrationSharing functionality (e.g., grep -r 'RegistrationSharing' /etc/smt/)Affected if RegistrationSharing is configured or enabled and the SMT version is below 3.0.37
-
Check SMT service status and logsRun 'systemctl status smt' and review /var/log/smt.log for any unusual SQL error messages or unexpected queries in the RegistrationSharing contextAffected if SQL errors or suspicious query patterns appear in logs and SMT version is below 3.0.37
You are affected if SUSE Subscription Management Tool is installed with a version lower than 3.0.37 and the RegistrationSharing module is present or enabled in your environment.
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 · scoped3.0.37
Upgrade SUSE Linux SMT to version 3.0.37 or later to patch the SQL injection vulnerability in the RegistrationSharing module.
3.0.37
- Backup the current SMT configuration and database before upgrading
- Update the SUSE package repository to ensure latest packages are available
- Upgrade the SMT (Subscription Management Tool) package to version 3.0.37 or later using the standard SUSE zypper update command (e.g., zypper update smt)
- Restart the SMT services after the upgrade completes
- Verify the RegistrationSharing module is functioning correctly and the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12470 — 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-2018-12470 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