CVE-2010-3719
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 · uneditedEval injection vulnerability in IMAdminSchedTask.asp in the administrative interface for Symantec IM Manager 8.4.16 and earlier allows remote attackers to execute arbitrary code via unspecified parameters to the ScheduleTask method.
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 confidenceEval injection vulnerability in IMAdminSchedTask.asp in the administrative interface for Symantec IM Manager 8.4.16 and earlier allows remote attackers to execute arbitrary code via unspecified parameters to the ScheduleTask method.
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<= 8.4.16= 6.0= 6.5= 7.0= 7.5= 8.3= 8.4.0= 8.4.1= 8.4.2= 8.4.5= 8.4.6= 8.4.7CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/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.
-
Confirm Symantec IM Manager is installedCheck for the presence of Symantec IM Manager on the system. Look for installation directories, services, or check the Windows Programs and Features list for 'Symantec IM Manager'.Affected if Symantec IM Manager is installed and the version matches <= 8.4.16 or equals any of 6.0, 6.5, 7.0, 7.5, 8.3, 8.4.0, 8.4.1, 8.4.2, 8.4.5, 8.4.6, 8.4.7
-
Locate and examine IMAdminSchedTask.aspSearch for the file IMAdminSchedTask.asp in the web application directory, typically under the administrative interface path. Common locations include /admin/ or /imadmin/ folders within the web root.Affected if The file IMAdminSchedTask.asp exists on the server, indicating the vulnerable component is present
-
Check web server accessibility of admin interfaceVerify whether the administrative web interface (where IMAdminSchedTask.asp resides) is accessible from the network. Check IIS or other web server configuration for the administrative application.Affected if The administrative interface is exposed to network access, allowing remote attackers to reach the vulnerable ScheduleTask method
-
Verify the eval() usage in the ASP fileIf file access is available, examine IMAdminSchedTask.asp for the presence of an eval() call within the ScheduleTask method that processes user-supplied parameters without proper validation.Affected if The vulnerable eval() call exists in the ScheduleTask method, confirming the code-level flaw is present
A user is affected if they are running any version of Symantec IM Manager at 8.4.16 or below and the administrative web interface with the vulnerable IMAdminSchedTask.asp file is network-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 dataUpdate to a patched version of Symantec IM Manager if available; otherwise, implement strict input validation on the ScheduleTask method parameters or remove the unsafe eval() call in the affected ASP file.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3719 — 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-2010-3719 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