CVE-2017-2745
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 · uneditedPotential security vulnerabilities have been identified with HP JetAdvantage Security Manager before 3.0.1. The vulnerabilities could potentially be exploited to allow stored cross-site scripting which could allow a hacker to execute scripts in a user's browser.
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 confidenceHP JetAdvantage Security Manager before version 3.0.1 contains a stored cross-site scripting (XSS) vulnerability. The flaw allows attackers to embed malicious scripts into the application which are then persisted and executed in the browsers of other users who access the affected functionality.
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.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
- 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 installed version of HP JetAdvantage Security ManagerAccess the application's administrative interface or check the product's About/Version information page within the software itself. If available, check installation directories for version metadata files or consult the software's built-in version reporting feature.Affected if The detected version is lower than 3.0.1 (for example, 3.0.0, 2.x, or any build prior to the 3.0.1 release).
-
Confirm the web interface is accessibleAttempt to access the HP JetAdvantage Security Manager login or dashboard URL in a browser. Verify the application responds and loads normally.Affected if The application is actively running and accessible to users, as stored XSS requires the malicious payload to be served to other users through the application's functionality.
-
Identify which application features accept user inputReview the application's available functions that accept and store user-supplied data (such as configuration fields, device settings, user profiles, or custom labels). These are the potential injection points for stored XSS.Affected if User input fields or configuration options exist and persist data, as the vulnerability specifically requires the attacker's script to be stored within the application and served to other users.
You are affected if HP JetAdvantage Security Manager is running at a version lower than 3.0.1 and the application web interface is accessible, as the stored XSS flaw exists in the application's data persistence functionality.
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 data3.0.1
Upgrade HP JetAdvantage Security Manager to version 3.0.1 or later to address this vulnerability. Additionally, implement output encoding and input validation as defense-in-depth measures.
- Consultation3.0 h
- Implementation4.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 $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2745 — 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-2745 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