CVE-2013-3627
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 · uneditedFrameworkService.exe in McAfee Framework Service in McAfee Managed Agent (MA) before 4.5.0.1927 and 4.6 before 4.6.0.3258 allows remote attackers to cause a denial of service (service crash) via a malformed HTTP request.
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 confidenceMcAfee Framework Service (FrameworkService.exe) in McAfee Managed Agent accepts HTTP requests and fails to properly handle malformed requests, causing the service to crash and resulting in denial of service. The vulnerability is exploitable remotely without authentication.
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.0, < 4.5.0.1927>= 4.6.0, < 4.6.0.3258CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Find McAfee Agent versionOpen Windows Registry and navigate to HKLM\SOFTWARE\McAfee\Agent, or run 'AgentVersion.exe' from the McAfee program directory, or use 'masvc.exe -version' from command lineAffected if Version is lower than 4.5.0.1927 (for 4.5.x branch) or lower than 4.6.0.3258 (for 4.6.x branch)
-
Verify FrameworkService.exe is runningOpen Task Manager or run 'tasklist | findstr FrameworkService' from command line, or check Services console for 'McAfee Framework Service'Affected if The service is present and running - this confirms the vulnerable component is active
-
Confirm remote management is enabledCheck if the agent has remote management/HTTP listener configured - look for 'EPO' or 'ePolicy Orchestrator' connection settings, or check if port 8443 or 443 is in use by masvc/FrameworkServiceAffected if Remote management is enabled and the service accepts HTTP connections - this is required for remote exploitation
-
Check for listening HTTP portsRun 'netstat -an | findstr "8443\|443\|8080"' or use a port scanner to check if the FrameworkService is listening on common management portsAffected if The service is bound to a network port and accessible over HTTP/HTTPS
-
Compare installed version to affected rangesIf version was obtained in step 1, verify it falls within: >= 4.5.0 and < 4.5.0.1927, OR >= 4.6.0 and < 4.6.0.3258Affected if Version number matches either of the two affected version ranges
System is vulnerable if McAfee Agent version is within the affected ranges (4.5.x before 4.5.0.1927 or 4.6.x before 4.6.0.3258) AND the Framework Service is running with remote management/HTTP enabled and accessible.
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 data4.5.0.19274.6.0.3258
Apply vendor patches: upgrade to McAfee Managed Agent 4.5.0.1927 or later for the 4.5 branch, or 4.6.0.3258 or later for the 4.6 branch.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3627 — 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-3627 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