CVE-2019-19003
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.2, the HTTPOnly flag is not set. This can allow Javascript to access the cookie contents, which in turn might enable Cross Site Scripting.
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.2 do not set the HTTPOnly flag on session cookies. This allows JavaScript to access cookie contents, enabling attackers who achieve XSS to steal authentication tokens or session identifiers.
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.2CVSS 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 the installed eSOMS versionAccess the eSOMS system administration panel or check the application banner/version endpoint. The version is typically displayed in the login page footer, about page, or system information section.Affected if The version displayed is 4.0, 4.x, 5.x, 6.0, 6.0.1, or 6.0.2, placing it within the affected range.
-
Verify version falls within affected rangeCompare the identified version against the affected range: versions 4.0 through 6.0.2 are vulnerable. Versions below 4.0 or above 6.0.2 are not affected by this specific CVE.Affected if The installed version is greater than or equal to 4.0 AND less than or equal to 6.0.2.
-
Inspect session cookie headersLog into eSOMS and use browser developer tools (Application tab > Cookies) or a proxy tool to capture the Set-Cookie response headers. Look for the session cookie (typically named JSESSIONID or similar) and check if the HTTPOnly attribute is present.Affected if The session cookie is set without the HTTPOnly flag, meaning the Set-Cookie header does not include the '; HttpOnly' or '; Secure; HttpOnly' suffix.
You are affected if your eSOMS version is between 4.0 and 6.0.2 inclusive AND your session cookies lack the HTTPOnly attribute in the Set-Cookie headers.
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 application to set the HTTPOnly attribute on all session cookies to prevent JavaScript access and mitigate XSS-driven cookie theft.
- Consultation6.0 h
- Implementation4.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 $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19003 — 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-19003 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