CVE-2019-3490
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 · uneditedA DOM based XSS vulnerability has been identified in the Netstorage component of Open Enterprise Server (OES) allowing a remote attacker to execute javascript in the victims browser by tricking the victim into clicking on a specially crafted link. This affects OES versions OES2015SP1, OES2018, and OES2018SP1. Older versions may be affected but were not tested as they are out of support.
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 confidenceA DOM-based Cross-Site Scripting (XSS) vulnerability exists in the Netstorage component of Open Enterprise Server. The vulnerability allows remote attackers to inject malicious JavaScript into web pages viewed by victims by tricking them into clicking specially crafted URLs. This occurs because user-supplied input is directly inserted into the DOM without proper sanitization or encoding.
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= 2015.1= 2018.0= 2018.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.
-
Verify Open Enterprise Server installationCheck if Micro Focus Open Enterprise Server is installed on the system by looking for OES-related processes, services, or installed packages using system inventory tools or package managers.Affected if Open Enterprise Server is not present on the system.
-
Determine installed OES versionRetrieve the installed version of Open Enterprise Server using system information commands or by checking installed software metadata. Compare your installed version to the affected ranges: 2015.1, 2018.0, and 2018.1.Affected if The installed version matches 2015.1, 2018.0, or 2018.1.
-
Confirm Netstorage component is enabledCheck if the Netstorage component is enabled and accessible on the OES server. This may involve examining the OES configuration, installed modules, or checking for Netstorage-related services or web applications.Affected if Netstorage is enabled and accessible.
-
Verify web interface exposureDetermine if the OES web interface (specifically Netstorage) is exposed to network access. Check firewall rules, web server configuration, and listening ports for Netstorage-related endpoints.Affected if The Netstorage web interface is accessible over the network.
The environment is affected if Open Enterprise Server versions 2015.1, 2018.0, or 2018.1 are installed with Netstorage enabled and the web interface is accessible.
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 dataApply vendor patches for OES2015SP1, OES2018, and OES2018SP1 when available. As an interim measure, advise users not to click untrusted links. Consider implementing Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3490 — 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-2019-3490 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