CVE-1999-0443
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 · uneditedPatrol management software allows a remote attacker to conduct a replay attack to steal the administrator password.
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 confidencePatrol management software contains a replay attack vulnerability in its authentication mechanism, allowing remote attackers to intercept and replay authentication requests to steal administrator passwords.
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= 3.2.3CVSS 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.
-
Identify BMC Patrol Agent versionLocate the BMC Patrol Agent installation directory and check for version information. On Windows, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\BMC Software\Patrol Agent\CurrentVersion or inspect the executable properties of patrol.exe. On Unix/Linux, run 'pkginfo -l PATROL' or check the installation logs.Affected if The installed version is exactly 3.2.3
-
Confirm Patrol Agent is running and accessibleCheck if the Patrol Agent process is running and listening on its management port (default TCP 3181 for Patrol Agent communications). Use 'netstat -an | grep 3181' or similar network diagnostic commands.Affected if The Patrol Agent is running and accepting remote connections on its management port
-
Verify authentication is enabledExamine the Patrol Agent configuration files (typically patrol.config or patrol.params in the installation directory) for authentication-related parameters. Look for settings that enable password-based authentication for remote management access.Affected if Remote password-based authentication is configured and enabled for the Patrol Agent
-
Check communication encryption statusInspect the Patrol Agent configuration for TLS/SSL settings. Look for parameters like 'ssl=', 'tls=', or 'encrypt=' and verify whether encrypted communication is enforced for authentication traffic.Affected if Authentication traffic is transmitted in plaintext without TLS encryption
You are affected if BMC Patrol Agent version 3.2.3 is installed with remote password-based authentication enabled and authentication traffic is not protected by TLS encryption.
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 dataImplement anti-replay protections such as cryptographic nonces, timestamps, or session tokens in the authentication flow, and ensure all authentication traffic is transmitted over encrypted channels using TLS.
- 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-1999-0443 — 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-1999-0443 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