CVE-2015-0795
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 · uneditedMultiple stack-based buffer overflows in the SafeShellExecute method in the NetIQExecObject.NetIQExec.1 ActiveX control in NetIQExec.dll in NetIQ Security Solutions for iSeries 8.1 allow remote attackers to execute arbitrary code via long arguments, aka ZDI-CAN-2699.
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 confidenceStack-based buffer overflow in the SafeShellExecute method of the NetIQExecObject.NetIQExec.1 ActiveX control (NetIQExec.dll) in NetIQ Security Solutions for iSeries 8.1 allows remote code execution via overly long arguments.
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= 8.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Locate NetIQExec.dll on the systemSearch for the file NetIQExec.dll across drives or in typical application installation directories. Check paths such as C:\Program Files\NetIQ or C:\Program Files (x86)\NetIQ. Use command: dir /s /b C:\NetIQExec.dll 2>nulAffected if The file NetIQExec.dll exists on the system
-
Check if the ActiveX control is registeredQuery the Windows Registry for the CLSID of the NetIQExecObject.NetIQExec.1 control. Check HKEY_CLASSES_ROOT\NetIQExecObject.NetIQExec.1 or use: reg query "HKEY_CLASSES_ROOT\NetIQExecObject.NetIQExec.1"Affected if The ActiveX control is registered in the Windows Registry
-
Verify the installed product versionCheck the installed version of NetIQ Security Solutions for iSeries or Micro Focus Security Solutions for iSeries. Look in Add/Remove Programs or check the product'sAbout or version information in the program menu.Affected if The installed version is Microfocus Security Solutions For Iseries 8.1
-
Check for web pages loading the vulnerable controlSearch for HTML or web files that reference the NetIQExec ActiveX control (look for <object> tags with classid CLSID:...). Use: findstr /s /i /m "NetIQExec" *.html *.asp *.aspx 2>nulAffected if Web pages on the server reference or instantiate the NetIQExecObject.NetIQExec.1 ActiveX control
The system is affected if NetIQExec.dll is present AND the NetIQExecObject.NetIQExec.1 ActiveX control is registered AND the installed version is 8.1 of the Security Solutions for iSeries product.
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 dataDisable or remove the vulnerable NetIQExec ActiveX control until vendor patches are available; deploy compensating controls such as network segmentation to limit exposure to attackers.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0795 — 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-2015-0795 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