CVE-2017-2989
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 · uneditedAdobe Campaign versions Build 8770 and earlier have an input validation bypass that could be exploited to read, write, or delete data from the Campaign database.
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 confidenceInput validation bypass in Adobe Campaign Build 8770 and earlier allows attackers to manipulate database queries through unsanitized input fields, potentially enabling unauthorized read, write, or delete operations on the Campaign database.
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<= 6.11CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Adobe Campaign versionLocate the installed Adobe Campaign build number or version number in the system documentation, installation directory, or campaign administration console. Common locations include the about page in the campaign client or server configuration files.Affected if The installed build number is 8770 or earlier, OR the version is 6.11 or earlier
-
Verify input validation configurationInspect the Adobe Campaign configuration files and settings related to input handling and query construction. Look for settings that control whether user-supplied input is validated before being used in database queries.Affected if Input validation is disabled, minimal, or not applied to user input fields used in database queries
-
Check accessible input interfacesIdentify all user-facing input interfaces in Adobe Campaign (such as web forms, API endpoints, or query builder interfaces) that accept user input and could potentially be used to construct database queries.Affected if Unsvalidated user input fields are accessible and can be manipulated to influence database query logic
-
Review database query handlingExamine how the Adobe Campaign application handles database queries, particularly any custom queries, reports, or filters that incorporate user-supplied values into SQL statements.Affected if User-supplied input is directly incorporated into database queries without parameterized query handling or proper sanitization
You are affected if your Adobe Campaign installation is version 6.11 or earlier (or build 8770 or earlier) AND user-supplied input fields can be used to manipulate database queries without proper validation or parameterized handling.
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 · scopedUpgrade Adobe Campaign to a version beyond Build 8770 that contains the security patch, or implement proper input validation and parameterized queries across all user-supplied input points.
Adobe Campaign 6.11 Build 8771 (or later within the 6.11.x line)
- Check the current Adobe Campaign build version in the installation (typically found in the About section or server configuration)
- Download and apply Adobe Campaign security patch APSB17-14 from Adobe's official support portal
- Verify the patch has been applied by confirming the build number is 8771 or later
- Test that the application functions normally after patching
- Verify database access controls are working correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2989 — 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-2017-2989 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