CVE-2014-9387
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 · uneditedSAP BusinessObjects Edge 4.1 allows remote attackers to obtain the SI_PLATFORM_SEARCH_SERVER_LOGON_TOKEN token and gain privileges via a crafted CORBA call, aka SAP Note 2039905.
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 confidenceSAP BusinessObjects Edge 4.1 contains an authentication bypass vulnerability where remote attackers can obtain the SI_PLATFORM_SEARCH_SERVER_LOGON_TOKEN token through specially crafted CORBA (Common Object Request Broker Architecture) calls, enabling unauthorized privilege escalation.
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= 4.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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 SAP BusinessObjects versionQuery the Central Management Console (CMC) or use the SAP BusinessObjects Lifecycle Manager to determine the exact installed version of SAP BusinessObjects. Alternatively, check the installation directory for version information or query the CMS database for the version metadata.Affected if The installed version is SAP BusinessObjects Edge 4.1 exactly (version = 4.1).
-
Determine if Platform Search Server is enabledAccess the Central Management Console (CMC) and navigate to the Platform Search Server settings. Verify whether the Platform Search Server service is currently running and enabled in the system configuration.Affected if The Platform Search Server functionality is enabled and running, as this is the component with the vulnerability.
-
Identify accessible CORBA portsReview network configuration and firewall rules to identify which ports are open for CORBA communication. Common CORBA ports in SAP BusinessObjects include 2809 and dynamic port ranges. Use netstat or port scanning tools to enumerate listening services.Affected if CORBA ports (used for inter-process communication in BusinessObjects) are exposed to untrusted networks or accessible from non-admin workstations.
-
Check for unauthorized SI_PLATFORM_SEARCH_SERVER_LOGON_TOKEN usageReview server logs and audit trails for any instances where the SI_PLATFORM_SEARCH_SERVER_LOGON_TOKEN was accessed or used outside of legitimate administrative sessions. Look for anomalous CORBA calls in system logs.Affected if The specific token SI_PLATFORM_SEARCH_SERVER_LOGON_TOKEN was obtained or used through crafted CORBA calls without proper authentication.
A user is affected if they are running SAP BusinessObjects Edge 4.1 with the Platform Search Server enabled and CORBA ports are network-accessible, allowing attackers to obtain the SI_PLATFORM_SEARCH_SERVER_LOGON_TOKEN through unauthorized CORBA calls.
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 the patch referenced in SAP Note 2039905. As an interim measure, restrict network access to CORBA ports and consider disabling the platform search server functionality if not required.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9387 — 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-9387 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