CVE-2007-2136
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 · uneditedStack-based buffer overflow in bgs_sdservice.exe in BMC Patrol PerformAgent allows remote attackers to execute arbitrary code by connecting to TCP port 10128 and sending certain XDR data, which is not properly parsed.
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 bgs_sdservice.exe in BMC Patrol PerformAgent allows remote attackers to execute arbitrary code by sending specially crafted XDR data to TCP port 10128, which is not properly validated before being copied to a stack buffer.
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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Verify BMC Patrol PerformAgent installationCheck for the presence of BMC Patrol PerformAgent by searching for the product directory (commonly in C:\Program Files\BMC Software\Patrol or /opt/bmc/Patrol) or querying installed software via system inventory toolsAffected if BMC Patrol PerformAgent is installed and the bgs_sdservice.exe component is present
-
Confirm bgs_sdservice.exe is runningOpen Task Manager or run 'tasklist | findstr bgs_sdservice' on Windows, or 'ps aux | grep bgs_sdservice' on Unix/Linux to check if the process is activeAffected if The bgs_sdservice.exe process is running on the system
-
Check if TCP port 10128 is listeningRun 'netstat -an | findstr 10128' or 'ss -tlnp | grep 10128' to determine if the service is bound to any network interfaceAffected if TCP port 10128 is in LISTEN state and accepting connections
-
Verify network exposure of the serviceCheck the binding address of the listening port using 'netstat -ano' or 'ss -tlnp' - determine if it listens on 0.0.0.0 (all interfaces) or a specific IP; also check firewall rules for inbound access to port 10128Affected if The service listens on 0.0.0.0 or an externally accessible IP, and firewall permits inbound connections to port 10128
If BMC Patrol PerformAgent is installed with bgs_sdservice.exe running and TCP port 10128 is exposed on the network, the system is affected by CVE-2007-2136.
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 dataRestrict network access to TCP port 10128 from untrusted sources; if possible, disable the bgs_sdservice.exe component until vendor patches can be applied.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2136 — 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-2007-2136 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