CVE-2019-17043
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 · uneditedAn issue was discovered in BMC Patrol Agent 9.0.10i. Weak execution permissions on the best1collect.exe SUID binary could allow an attacker to elevate his/her privileges to the ones of the "patrol" user by specially crafting a shared library .so file that will be loaded during execution.
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 confidenceThe BMC Patrol Agent 9.0.10i best1collect.exe binary is configured with SUID permissions but has weak execution permissions that allow privilege escalation. An attacker can exploit this by placing a malicious shared library (.so file) that the SUID binary will load during execution, effectively executing code with the elevated privileges of the 'patrol' user.
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= 9.0.10iCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Verify BMC Patrol Agent installation and versionLocate the best1collect.exe binary on the system using 'find / -name best1collect.exe 2>/dev/null' or check common installation paths like /opt/bmc or /usr/local/patrol. Check the installed version using 'file best1collect.exe' or check version info in the installation directory.Affected if The binary is found and its version matches 9.0.10i exactly.
-
Check SUID permissions on best1collect.exeRun 'ls -la /path/to/best1collect.exe' (replace with actual path) and look for 's' in the owner execute field (e.g., -rwsr-xr-x).Affected if The file has SUID bit set (shows 's' instead of 'x' in owner permissions) and is owned by root or patrol user.
-
Check file permissions for weaknessExamine the permission bits from the ls -la output. Look for world-writable permissions (w in others column) or group-writable permissions that could allow non-root users to modify the binary or its directory.Affected if The binary or its directory has weak permissions such as world-writable (777) or group-writable that permits modification by non-privileged users.
-
Check for library loading pathsUse 'ldd best1collect.exe' to see which libraries it loads, and check if any directories in the load path are writable by non-privileged users. Also check if the binary runs from a directory that regular users can write to.Affected if The binary loads shared libraries from writable directories accessible to non-root users, enabling library hijacking.
-
Verify binary ownership and directory securityCheck that the binary is owned by root with 'ls -la /path/to/best1collect.exe' and that parent directories have restricted permissions (755 or stricter) to prevent modification.Affected if The binary is owned by a non-root user (such as patrol) or parent directories have weak permissions allowing unauthorized modification.
You are affected if BMC Patrol Agent version 9.0.10i is installed with the best1collect.exe binary having SUID permissions and weak ownership/permissions that permit library hijacking by non-privileged users.
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 dataRemove the SUID bit from best1collect.exe if not strictly required, or ensure the binary runs from a secure location with restricted write permissions to prevent library hijacking, and verify proper file ownership and permissions (e.g., chmod 755 with root ownership).
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17043 — 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-2019-17043 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