CVE-2020-14248
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 · uneditedBigFix Inventory up to v10.0.2 does not set the secure flag for the session cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this cookie.
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 confidenceBigFix Inventory up to v10.0.2 fails to set the Secure flag on session cookies during HTTPS sessions, allowing the cookie to be transmitted over insecure HTTP connections and making it vulnerable to interception via man-in-the-middle attacks.
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>= 9.0.0, <= 10.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 BigFix Inventory versionLocate the installed BigFix Inventory version in the console or check the installation directory for version information. On Windows this may be in the installation path, or use the BigFix console to view version details under the Help or About section.Affected if The installed version is between 9.0.0 and 10.0.2 inclusive.
-
Confirm HTTPS access is enabledVerify that the BigFix web interface is configured to accept HTTPS connections. This is typically configured in the WebSphere application server settings or the BigFix server configuration.Affected if HTTPS access is enabled and users connect to BigFix over HTTPS.
-
Capture HTTPS session cookie headersAccess the BigFix web interface over HTTPS using a browser or HTTP proxy tool (such as browser developer tools or curl with -k -v flags). Inspect the Set-Cookie headers in the HTTP response to identify the session cookie.Affected if A session cookie is returned in the HTTPS response.
-
Verify Secure flag on session cookieExamine the Set-Cookie header for the session cookie. Look for the Secure attribute (e.g., Set-Cookie: JSESSIONID=...; Secure). Check if the Secure flag is present in the cookie definition.Affected if The session cookie Set-Cookie header does NOT contain the Secure attribute, meaning the cookie can be sent over insecure HTTP connections.
A user is affected if they run BigFix Inventory version 9.0.0 through 10.0.2 with HTTPS enabled and the session cookie lacks the Secure flag in the Set-Cookie 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 application server (WebSphere) to set the Secure attribute on session cookies, or upgrade BigFix Inventory to a version beyond v10.0.2 where this issue is resolved.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14248 — 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-2020-14248 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