CVE-2017-18268
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 · uneditedSymantec IntelligenceCenter 3.3 is vulnerable to the Return of the Bleichenbacher Oracle Threat (ROBOT) attack. A remote attacker, who has captured a pre-recorded SSL session inspected by SSLV, can establish large numbers of crafted SSL connections to the target and obtain the session keys required to decrypt the pre-recorded SSL session.
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 confidenceSymantec IntelligenceCenter 3.3 is vulnerable to the ROBOT attack, a variant of the Bleichenbacher oracle attack on RSA key exchange in SSL/TLS. An attacker who has captured a pre-recorded SSL session can send crafted SSL connections with modified padding to infer plaintext information and eventually derive the session keys needed to decrypt the captured traffic.
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.3CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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.
-
Confirm installed version of Symantec IntelligenceCenterCheck the installed version through the product's about page, software inventory, or by querying the application binary metadata. The affected version is 3.3.Affected if The installed version is exactly 3.3
-
Identify SSL/TLS configuration locationLocate the SSL/TLS configuration files or registry settings where cipher suites are defined for the Symantec IntelligenceCenter web server or service.Affected if RSA key exchange cipher suites (such as TLS_RSA_WITH_*) are found in the enabled cipher list
-
Test for RSA key exchange supportUse an SSL/TLS testing tool such as nmap with the ssl-enum-ciphers script, or OpenSSL s_client to connect to the service and enumerate supported cipher suites. Look for any RSA key exchange ciphers in the output.Affected if The server accepts or offers RSA key exchange cipher suites during negotiation
-
Verify server response to malformed RSA paddingSend a TLS handshake with modified padding using a ROBOT attack testing tool (such as test-robot or a custom script) and observe if the server returns distinguishable error messages or timing differences consistent with a Bleichenbacher oracle.Affected if The server exhibits oracle behavior (specific error types or timing leaks) in response to malformed padding
The environment is affected if Symantec IntelligenceCenter version 3.3 is running AND RSA key exchange cipher suites are enabled and the server responds to padding oracle probes.
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 a patched version of Symantec IntelligenceCenter, or disable RSA key exchange cipher suites in favor of forward-secret options like ECDHE, and verify the configuration through SSL/TLS testing tools.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18268 — 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-18268 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