CVE-2013-5867
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 · uneditedUnspecified vulnerability in the Siebel Core - Server Infrastructure component in Oracle Siebel CRM 8.1.1 and 8.2.2 allows remote attackers to affect availability via vectors related to SISNAPI & Network Infrastructure.
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 confidenceVulnerability in Oracle Siebel CRM versions 8.1.1 and 8.2.2 affecting the Siebel Core - Server Infrastructure component, specifically the SISNAPI (Siebel Network Protocol API) and Network Infrastructure. The unspecified flaw allows remote attackers to impact system availability, likely through malformed network requests to the SISNAPI interface.
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.1.1= 8.2.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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify Oracle Siebel CRM installationLook for Siebel installation directories such as C:\Siebel or /opt/siebel, or check for Siebel services in the Windows Services list or Unix service manager.Affected if No Siebel installation found means this CVE does not apply.
-
Determine installed Siebel versionCheck the Siebel version file typically located in the Siebel root directory (e.g., VERSION.txt, about.htm, or srmlog.txt). In Windows, you can also check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Siebel\Siebel Enterprise Server. Compare your version to 8.1.1 or 8.2.2.Affected if If the installed version is exactly 8.1.1 or 8.2.2, the system is running a vulnerable version.
-
Verify SISNAPI component is enabledCheck if the Siebel Gateway and/or Siebel Server components responsible for SISNAPI are running. Look for processes like siebel.exe, smgr.exe, or check the Siebel Enterprise Server configuration files (e.g., eapps.cfg, siebproc.dat).Affected if If SISNAPI is disabled or not configured, the vulnerability may not be exploitable even on a vulnerable version.
-
Check network exposure of SISNAPI portsVerify if the Siebel server is listening on TCP ports 49152-65535 (the default SISNAPI port range). Use netstat -an or equivalent command to list open ports and check if these ports are bound to non-localhost interfaces. Test remote connectivity to these ports using telnet or nmap.Affected if If SISNAPI ports are exposed to untrusted network addresses, the system is vulnerable to remote availability impact.
A user is affected if they have Oracle Siebel CRM versions 8.1.1 or 8.2.2 with the SISNAPI component enabled and exposed to network access.
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 dataApply Oracle Critical Patch Update CPUOct2013 or later. If patching is not immediately feasible, restrict network access to Siebel server SISNAPI ports (TCP 49152-65535 by default) to trusted IPs only.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5867 — 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-2013-5867 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