CVE-2013-0140
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 · uneditedSQL injection vulnerability in the Agent-Handler component in McAfee ePolicy Orchestrator (ePO) before 4.5.7 and 4.6.x before 4.6.6 allows remote attackers to execute arbitrary SQL commands via a crafted request over the Agent-Server communication channel.
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 confidenceSQL injection vulnerability in McAfee ePolicy Orchestrator's Agent-Handler component allows remote attackers to execute arbitrary SQL commands via crafted requests over the Agent-Server communication channel. The vulnerability affects ePO versions before 4.5.7 and 4.6.x before 4.6.6.
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.5.6= 2.0= 2.5= 2.5.1= 3.0= 3.5.0= 3.6.0= 3.6.1= 4.0= 4.5.0= 4.5.3= 4.5.4CVSS 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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:M/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.
-
Locate ePolicy Orchestrator versionAccess the ePO console and navigate to the Server Settings page, or check the ePO installation directory for a version file. The version is typically displayed in the console header or in the orion.log file.Affected if The displayed version matches any of these: 2.0, 2.5, 2.5.1, 3.0, 3.5.0, 3.6.0, 3.6.1, 4.0, 4.5.0, 4.5.3, 4.5.4, or any version 4.5.6 or lower, or any 4.6.x version before 4.6.6.
-
Verify Agent-Handler component is in useConfirm that the ePO server is configured as an Agent-Handler. This component handles Agent-Server communication. Check the ePO architecture to see if this server acts as an Agent-Handler rather than a Managed Client or Agent.Affected if The ePO server is configured to handle agent communications, meaning it functions as an Agent-Handler in the ePO hierarchy.
-
Check for direct agent communication exposureReview the Agent-Server communication settings to determine if agents can communicate directly with this Handler over the network without additional security controls or authentication layers.Affected if Agents are permitted to communicate directly with the Agent-Handler component without restricted policy enforcement or additional authentication barriers.
-
Compare installed version to fixed releasesIdentify the exact build number and compare it to the fixed versions 4.5.7 and 4.6.6. The exact version is visible in the ePO console under the Software ID or in the ePO installer properties.Affected if The installed version is lower than 4.5.7 (for the 4.5.x branch) or lower than 4.6.6 (for the 4.6.x branch).
You are affected if your ePO version matches the listed vulnerable versions AND the Agent-Handler component is active in your environment, enabling the SQL injection attack vector in the Agent-Server communication channel.
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 dataUpgrade to ePO 4.5.7 or 4.6.6 or later to remediate this vulnerability; alternatively, apply vendor-supplied patches if available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0140 — 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-0140 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