CVE-2015-7291
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 · uneditedCross-site request forgery (CSRF) vulnerability in adv_pwd_cgi in the web management interface on Arris DG860A, TG862A, and TG862G devices with firmware TS0703128_100611 through TS0705125D_031115 allows remote attackers to hijack the authentication of arbitrary users.
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 confidenceCross-site request forgery (CSRF) vulnerability in the adv_pwd_cgi endpoint of the web management interface on Arris DG860A, TG862A, and TG862G cable gateway devices with firmware versions TS0703128_100611 through TS0705125D_031115 allows remote attackers to hijack user authentication by tricking authenticated users into visiting malicious pages that send forged requests to the device.
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= ts070593c_073013= ts0703128_100611= ts0703135_112211= ts0705125_062314= ts0705125d_031115CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/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.
-
Identify the device modelCheck the device label or access the web management interface to confirm the model is Arris DG860A, TG862A, or TG862GAffected if Device model is one of these three models
-
Check the firmware versionAccess the web management interface status page or check the device label for the firmware version string (e.g., TS0703128_100611, TS0705125D_031115, etc.)Affected if Firmware version is TS0703128_100611 through TS0705125D_031115, or exactly matches ts070593c_073013, ts0703128_100611, ts0703135_112211, ts0705125_062314, or ts0705125d_031115
-
Verify web management interface is accessibleAttempt to access the device's web interface on the default IP (typically 192.168.0.1 or 192.168.1.1) via HTTPAffected if Web management interface is reachable and responds to HTTP requests
-
Confirm adv_pwd_cgi endpoint existsAccess the URL path /adv_pwd_cgi on the device's web interface to see if the endpoint respondsAffected if The adv_pwd_cgi endpoint returns a response (indicating the vulnerable script is present)
If the device is an Arris DG860A/TG862A/TG862G with firmware between TS0703128_100611 and TS0705125D_031115 and the web management interface is accessible, the device is affected by this CSRF vulnerability.
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 dataImplement anti-CSRF tokens/validation in the web management interface; users should avoid browsing untrusted sites while authenticated to the device; contact Arris for firmware updates.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7291 — 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-2015-7291 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