CVE-2011-3197
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 · uneditedSQL injection vulnerability in Domain Technologie Control (DTC) before 0.34.1 allows remote authenticated users to execute arbitrary SQL commands via the addrlink parameter to shared/inc/forms/domain_info.php. NOTE: CVE-2011-3197 has been SPLIT due to findings by different researchers. CVE-2011-5272 has been assigned for the vps_note parameter to dtcadmin/logPushlet.php vector.
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 confidenceSQL injection vulnerability in Domain Technologie Control (DTC) before version 0.34.1 allows remote authenticated users to execute arbitrary SQL commands via the addrlink parameter in shared/inc/forms/domain_info.php.
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<= 0.32.11= 0.24.6= 0.25.1= 0.25.2= 0.25.3= 0.26.7= 0.26.8= 0.26.9= 0.27.3= 0.28.2= 0.28.3= 0.28.4CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 if DTC is installedLook for Domain Technologie Control installation directories, typically under /var/www/dt c or /usr/local/dtc, or check for DTC-related processes and web server configurations.Affected if DTC is not installed on the system.
-
Determine installed DTC versionCheck the DTC version file or package - common locations include a version file in the DTC root directory, or run 'dpkg -l | grep dtc' (Debian) or 'rpm -qa | grep dtc' (RPM-based systems).Affected if The installed version is <= 0.32.11 OR equals any of: 0.24.6, 0.25.1, 0.25.2, 0.25.3, 0.26.7, 0.26.8, 0.26.9, 0.27.3, 0.28.2, 0.28.3, 0.28.4.
-
Verify vulnerable file existsCheck for the presence of shared/inc/forms/domain_info.php in the DTC web root directory.Affected if The file exists and the version is in the affected range.
-
Confirm remote access is enabledVerify the DTC web interface is accessible remotely (not restricted to localhost) and user authentication is enabled.Affected if The web interface accepts remote connections and allows user login.
A user is affected if Domain Technologie Control is installed with a version <= 0.32.11 or matching any of the specific point versions (0.24.6, 0.25.1, 0.25.2, 0.25.3, 0.26.7, 0.26.8, 0.26.9, 0.27.3, 0.28.2, 0.28.3, 0.28.4), the vulnerable PHP file exists, and the web interface is accessible to remote authenticated users.
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 dataUpgrade to DTC version 0.34.1 or later which contains the patch, or implement proper input validation and parameterized queries for the addrlink parameter in the affected file.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3197 — 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-2011-3197 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