Security readout for executives and security teams
Plain-English summary
IBM BigFix Platform versions 9.2.0 through 9.2.14 and 9.5 through 9.5.9 may send authorization or session cookies without the Secure flag. This can expose cookie values over unencrypted HTTP traffic and may allow account/session compromise in specific network conditions.
Executive priority
Treat as a targeted confidentiality risk, not an emergency. Prioritize remediation for internet-adjacent, administrator-facing, or shared-network BigFix deployments because exposed session cookies can undermine administrative trust.
Technical view
The issue is missing Secure attributes on authorization tokens or session cookies in affected IBM BigFix Platform releases. The CVSS v3.0 score is 3.7, with network attack vector, high attack complexity, low confidentiality impact, and no integrity or availability impact recorded.
Likely exposure
Exposure is limited to organizations running IBM BigFix Platform 9.2.0-9.2.14 or 9.5-9.5.9. Risk is higher where users can reach BigFix over HTTP paths or where network traffic can be observed.
Exploitation context
The source bundle does not indicate active exploitation, and this CVE is not marked as CISA KEV. Exploitation depends on cookie transmission over insecure HTTP and the ability to observe that traffic.
Researcher notes
Evidence is limited to the CVE record, IBM advisory reference, and IBM X-Force entry. No CWE is listed. The bundle identifies affected version ranges but does not provide detailed patch-version text beyond the IBM remediation reference.
Mitigation direction
- Identify all IBM BigFix Platform versions in use.
- Review IBM advisory ibm10733605 for official remediation guidance.
- Upgrade or remediate affected releases according to IBM guidance.
- Ensure BigFix access is restricted to HTTPS-only paths where supported.
- Limit access to BigFix administrative interfaces to trusted networks.
Validation and detection
- Confirm no BigFix Platform instances run affected versions.
- Verify session and authorization cookies include the Secure attribute.
- Check whether any BigFix endpoints remain reachable over HTTP.
- Review proxy or access logs for unexpected HTTP access to BigFix hosts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-1484 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/A:N/AC:H/AV:N/C:L/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/A:N/AC:H/AV:N/C:L/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O2.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
3.7LowVector: CVSS:3.0/A:N/AC:H/AV:N/C:L/I:N/PR:N/S:U/UI:N/E:U/RC:C/RL:O
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/docview.wss?uid=ibm10733605CVE reference · x_refsource_CONFIRM
- ibm-bigfix-cve20181484-info-disc(140969)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
