CVE-2016-1035
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 RoboHelp Server 9 before 9.0.1 mishandles SQL queries, which allows attackers to obtain sensitive information via unspecified vectors.
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 confidenceSQL injection vulnerability in Adobe RoboHelp Server 9 versions before 9.0.1 allows unauthenticated attackers to execute arbitrary SQL queries and obtain sensitive information from the database through improperly handled SQL query inputs.
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= 9= 9.0.0.228= 9.0.1CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Verify Adobe RoboHelp Server is installedCheck for the presence of Adobe RoboHelp Server on the system. Look for the service named 'RoboHelp Server' in Windows Services, or check for the installation directory (typically under C:\Program Files\Adobe\ or C:\Program Files (x86)\Adobe\). On Linux, check /opt/ or /usr/local/ for a RoboHelp Server directory.Affected if The software is not installed, the vulnerability does not apply.
-
Determine the installed versionLocate the version information in the installation directory. Common locations include a version file, about dialog, or the Windows registry under HKLM\SOFTWARE\Adobe\RoboHelp Server. The version may also be visible in the application's web interface if accessible.Affected if The exact version cannot be determined or verified.
-
Compare version against affected rangeThe vulnerability affects versions before 9.0.1. Compare your installed version to: 9.0.0, 9.0.0.228 (affected versions). Version 9.0.1 is the patched release. If your version is 9.0.0.x or earlier, you are within the affected range.Affected if Installed version is 9.0.0.x or any version below 9.0.1.
-
Assess network exposure of the web interfaceSince this is an unauthenticated SQL injection vulnerability, determine if the RoboHelp Server web interface is accessible from the network. Check firewall rules, IIS/Apache configuration, and listening ports (default HTTP port 80 or 8080).Affected if The web interface is exposed to untrusted networks without authentication barriers.
You are affected if Adobe RoboHelp Server version 9.0.0.x is installed and its web interface is network-accessible, because the CVE permits unauthenticated SQL injection against these vulnerable versions.
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 Adobe RoboHelp Server to version 9.0.1 or later to apply the vendor patch that addresses the SQL injection vulnerability.
- 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-2016-1035 — 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-2016-1035 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