CVE-2017-1000035
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 · uneditedTiny Tiny RSS before 829d478f is vulnerable to XSS window.opener attack
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 confidenceTiny Tiny RSS before commit 829d478f contains a Cross-Site Scripting vulnerability via the window.opener object. When the application opens external links in new browser tabs or windows, the opened page can potentially manipulate the originating page through window.opener, allowing script execution in the context of the trusted Tiny Tiny RSS site.
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 dataall versionsCVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Tiny Tiny RSS versionCheck the version.php file in the tt-rss root directory, or run `git log --oneline -1` if using gitAffected if The installed version is before commit 829d478f or the version cannot be determined to be at/after that commit
-
Check for rel=noopener noreferrer in link codeSearch the codebase for external link generation: look for patterns like 'window.open' or anchor tags pointing to external URLs in files such as functions.php, view.php, or plugin filesAffected if External links opened via window.open() or anchor tags lack the noopener and noreferrer rel attributes
-
Inspect headline/external link handlingExamine the code that handles displaying headlines or excerpts with external links - typically in lib/xmlphp.php or similar rendering files - to verify if link() or similar helper functions include rel="noopener noreferrer"Affected if The code that generates external links in headlines, excerpts, or user-generated content does not add rel="noopener noreferrer" attributes
-
Verify link rendering in affected viewsView the HTML source of pages containing external links (such as the headline view or any feed content with external URLs) and inspect anchor tags for target="_blank" to confirm they include rel="noopener noreferrer"Affected if Links that open in new tabs (target=_blank) are missing the rel="noopener noreferrer" attribute in the rendered HTML
You are affected if your Tiny Tiny RSS installation is before commit 829d478f AND external links in the application are missing rel="noopener noreferrer" attributes on links that open in new browser tabs.
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 dataAdd rel="noopener noreferrer" attribute to all links that open new browser windows/tabs, or use window.open() with the noopener feature set, to prevent the opened page from accessing the originating window object.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000035 — 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-1000035 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