SentinelApplication · Microfocus

CVE-2018-7675

MEDIUM · 5.3 CVSS v3.0 Published 2018-03-07
Fix available
A fix is available. Upgrade to after 8.1 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
In NetIQ Sentinel before 8.1.x, a Sentinel user is logged into the Sentinel Web Interface. After performing some tasks within Sentinel the user does not log out but does go idle for a period of time. This in turn causes the interface to timeout so that it requires the user to re-authenticate. If another user is passing by and decides to login, their credentials are accepted. While The user does not inherit any of the other users privileges, they are able to view the previous screen. In this case it is possible that the user can see another users events or configuration information for whatever view is currently showing.

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 · moderate confidence

In NetIQ Sentinel before 8.1.x, after a user's session times out due to inactivity, the web interface fails to properly clear the previous user's data from the display. When a new user authenticates, they can see the prior user's screen content including events and configuration information. This is a session management and screen-clearing failure on timeout.

MitigationUpgrade to NetIQ Sentinel 8.1.x or later, which implements proper session cleanup and screen clearing upon timeout to prevent data disclosure between users.

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
SentinelApplication
Affected:<= 8.1

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Sentinel installation version
    Locate the Sentinel installation directory and check the version information file, or use the Sentinel administrative interface to view the installed version number
    Affected if The installed version is 8.1 or any version prior to 8.1.x (for example, 8.0.x, 7.x, etc.)
  2. Confirm version via productAbout or system info
    Access the Sentinel web interface admin panel and navigate to the About or System Information section to retrieve the exact build and version number
    Affected if The version displayed shows a build number or version string that is 8.1 or lower
  3. Verify session timeout configuration
    Check the Sentinel configuration files (typically in the conf or config directory) for session timeout settings and confirm timeout is enabled
    Affected if Session timeout is configured and the software version is 8.1 or earlier
  4. Test timeout behavior (optional confirmation)
    Log into the Sentinel web interface, wait for session timeout due to inactivity, then log in as a different user and observe if previous user's screen data is visible
    Affected if After timeout and re-login, the new user sees residual data from the previous user's session (this confirms the vulnerability is active)

The environment is affected if the installed NetIQ Sentinel version is 8.1 or any version prior to 8.1.x, as the session cleanup flaw only exists in versions up to 8.1.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 8.1
Interim mitigation

Upgrade to NetIQ Sentinel 8.1.x or later, which implements proper session cleanup and screen clearing upon timeout to prevent data disclosure between users.

Fix this in Sentinel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7675 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7675 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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