CVE-2014-9768
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 · uneditedIBM Tivoli NetView Access Services (NVAS) allows remote authenticated users to gain privileges by entering the ADM command and modifying a "page ID" field to the EMSPG2 transaction code. NOTE: the vendor's perspective is that configuration and use of available security controls in the NVAS product mitigates the reported vulnerability
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 confidenceIBM Tivoli NetView Access Services (NVAS) contains a privilege escalation vulnerability where remote authenticated users can enter the ADM command and modify a 'page ID' field to the EMSPG2 transaction code, thereby gaining elevated privileges beyond what their account should normally permit.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm NVAS is installed and runningCheck if IBM Tivoli NetView Access Services is installed on the system by looking for NVAS processes, services, or binaries. On Windows, check Services panel for 'NetView Access Services'; on UNIX/Linux, check for nvas processes via 'ps aux | grep -i nvas' or look for NVAS installation directories.Affected if NVAS is installed and running on the system
-
Identify user access to ADM commandExamine the NVAS configuration or user role assignments to determine which users or groups have access to the ADM administrative command. Check NVAS user configuration files, role definitions, or access control lists that grant command-level permissions.Affected if Authenticated users have permission to execute the ADM command
-
Verify EMSPG2 transaction code accessibilityCheck NVAS transaction code configuration to determine if the EMSPG2 transaction code is available and accessible to standard users. Inspect the transaction code registry or configuration where page IDs and transaction codes are defined.Affected if The EMSPG2 transaction code is defined and accessible to non-administrative users
-
Review user role assignments for privilege escalation pathsAudit the current user role assignments in NVAS to identify if any authenticated users have roles that could be combined with the ADM command and EMSPG2 modification to achieve elevated privileges. Look for users assigned to roles that permit both command execution and transaction code manipulation.Affected if Any authenticated non-administrative user has roles that permit both ADM command access and ability to modify page ID fields to EMSPG2
-
Check security control configurationInspect NVAS security controls related to administrative function access and transaction code restrictions. Look for configuration settings that control whether administrative functions and transaction codes are properly restricted.Affected if Security controls are absent, misconfigured, or do not restrict access to administrative functions and the EMSPG2 transaction code
A user is affected if NVAS is running and allows authenticated users to access the ADM command while also permitting modification of page ID fields to reference the EMSPG2 transaction code, enabling privilege escalation beyond their assigned role.
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 dataImplement and properly configure available NVAS security controls to restrict access to administrative functions and transaction codes. Review user role assignments and enforce least-privilege access policies.
- Consultation8.0 h
- Implementation12.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9768 — 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-2014-9768 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