CVE-2019-19089
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 · uneditedFor ABB eSOMS versions 4.0 to 6.0.3, the X-Content-Type-Options Header is missing in the HTTP response, potentially causing the response body to be interpreted and displayed as different content type other than declared. A possible attack scenario would be unauthorized code execution via text interpreted as JavaScript.
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 confidenceABB eSOMS versions 4.0 to 6.0.3 fail to include the X-Content-Type-Options HTTP header in responses, enabling browsers to perform MIME type sniffing. This can cause text content to be interpreted as executable JavaScript, potentially leading to XSS and unauthorized code execution.
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>= 4.0, <= 6.0.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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/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 Esoms versionAccess the Esoms administration interface or check system inventory for the Hitachi Energy Esoms application. Look in version information panels, about pages, or product documentation shipped with the installation.Affected if The installed version is between 4.0 and 6.0.3 inclusive.
-
Verify X-Content-Type-Options header presenceUse a web browser developer tool, curl, or a network proxy to capture an HTTP response from the Esoms web server. Inspect the response headers for 'X-Content-Type-Options'.Affected if The header 'X-Content-Type-Options: nosniff' is missing from HTTP responses.
-
Test for MIME type sniffing vulnerabilityHost a text file containing JavaScript code on the Esoms server and attempt to access it via a browser. Observe whether the browser executes the content as JavaScript rather than treating it as plain text.Affected if The server allows text content to be executed as JavaScript due to missing Content-Type or nosniff header.
-
Check web server configuration for headerInspect the web server configuration files (such as httpd.conf, nginx.conf, or the application's web.xml) for any directive that sets the X-Content-Type-Options header.Affected if No configuration directive sets 'X-Content-Type-Options: nosniff' on responses.
You are affected if you run Hitachi Energy Esoms version 4.0 through 6.0.3 and HTTP responses from the server lack the 'X-Content-Type-Options: nosniff' header.
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 dataConfigure the web server to include the header 'X-Content-Type-Options: nosniff' on all HTTP responses to prevent MIME type sniffing.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19089 — 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-19089 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