var-201012-0127
Vulnerability from variot
The GetStringAMSHandler function in prgxhndl.dll in hndlrsvc.exe in the Intel Alert Handler service (aka Symantec Intel Handler service) in Intel Alert Management System (AMS), as used in Symantec Antivirus Corporate Edition 10.1.4.4010 on Windows 2000 SP4 and Symantec Endpoint Protection before 11.x, does not properly validate the CommandLine field of an AMS request, which allows remote attackers to cause a denial of service (application crash) via a crafted request. Symantec Antivirus is prone to a remote denial-of-service vulnerability. An attacker can exploit this issue to crash the affected application, denying service to legitimate users. Symantec Antivirus Corporate Edition 10.1.4.4010 is vulnerable; other versions may also be affected. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Core Security Technologies - CoreLabs Advisory
http://corelabs.coresecurity.com/
Symantec Intel Handler Service Remote DoS
- Advisory Information
Title: Symantec Intel Handler Service Remote DoS Advisory Id: CORE-2010-0728 Advisory URL: [http://www.coresecurity.com/content/symantec-intel-handler-service-remote-dos]
Date published: 2010-12-13 Date of last update: 2010-12-13 Vendors contacted: Symantec Release mode: User release
- Vulnerability Information
Class: Input validation error [CWE-20] Impact: Denial of service Remotely Exploitable: Yes Locally Exploitable: No CVE Name: CVE-2010-3268 Bugtraq ID: N/A
-
A source address in a 'MOV' instruction is calculated from values present in the request, causing a remote denial-of-service.
-
Vulnerable packages
. Older versions are probably affected too, but they were not checked.
-
Non-vulnerable packages
-
During the SEP 11.x engineering phase SEP was rewritten so that it no longer uses Intel AMS code. The installation of AMS is disabled by default for SEP versions that include it. The only workaround is to disable Intel AMS.
-
Credits
This vulnerability was discovered and researched by Nahuel Riva from Core Security Technologies. Publication was coordinated by Jorge Lucangeli Obes.
- Technical Description / Proof of Concept Code
The request is handled in 'prgxhndl.dll', called from 'hndlsrvc.exe', more specifically from function '0x501A105D':
/----- 501A105D /. 55 PUSH EBP 501A105E |. 8BEC MOV EBP,ESP 501A1060 |. 81EC 60040000 SUB ESP,460 501A1066 |. 8D45 F4 LEA EAX,DWORD PTR SS:[EBP-C] 501A1069 |. 57 PUSH EDI 501A106A |. 50 PUSH EAX 501A106B |. 68 34301A50 PUSH prgxhndl.501A3034 ; ASCII "CommandLine" 501A1070 |. FF75 0C PUSH DWORD PTR SS:[EBP+C] 501A1073 |. 8BF9 MOV EDI,ECX 501A1075 |. FF75 08 PUSH DWORD PTR SS:[EBP+8] 501A1078 |. E8 33010000 CALL JMP.&HNDLRSVC.#17_?GetString@AMSHandler@@QAEHPAXKPADPAPAD@Z
- -----/ Inside that function, 'GetStringAMSHandler()' is called to parse the content of the 'CommandLine' field present in the request. In turn, 'GetStringAMSHandler()' forwards the request to function 'AMSLIB.18' present in 'AMSLIB.dll', and this function ends up calling the function that crashes, 'AMSGetPastParamList()', also in 'AMSLIB.dll':
/----- 500733AE |. 8B45 E4 MOV EAX,DWORD PTR SS:[EBP-1C] 500733B1 |. 50 PUSH EAX ; /Arg1 500733B2 |. E8 54F3FFFF CALL AMSLIB.AMSGetPastParamList ; \AMSGetPastParamList
- -----/ The crash occurs at address '0x5007278B':
/----- 50072786 |. 8B45 F0 |MOV EAX,DWORD PTR SS:[EBP-10] 50072789 |. 33C9 |XOR ECX,ECX 5007278B |. 8A08 |MOV CL,BYTE PTR DS:[EAX] 5007278D |. 85C9 |TEST ECX,ECX 5007278F |. 75 16 |JNZ SHORT AMSLIB.500727A7
-
-----/ When trying to read at the memory area pointed to by EAX, this value is invalid and the service crashes. This part of the code is parsing (inside a loop) the argument passed in the 'CommandLine' parameter. It seems that in many parts of the loop the pointer that is loaded from '[EBP-10]' is calculated from a value present in the request.
-
Report Timeline
. 2010-08-12: Initial notification sent to Symantec. 2010-08-19: Given that there was no answer since the initial notification, Core requests a confirmation of reception. 2010-08-19: Vendor replies that the initial notification was not received. 2010-08-20: Core resends original advisory draft. 2010-08-20: Vendor acknowledges reception of advisory draft. 2010-08-25: Vendor replies that the issue looks like a duplicate of another one, already planned to be fixed in a September/October timeframe. Vendor will investigate further and give a definite reply. 2010-08-26: Core acknowledges this reply. 2010-08-26: Vendor confirms that the issue is a duplicate, but will give credit to Nahuel Riva as "secondary finder". Vendor asks to postpone the publication of the advisory until a fix is released. 2010-08-27: Core agrees to postpone the publication of the advisory, given that an estimate release date for the fix is provided. 2010-08-27: Vendor replies with an estimated release date for the end of September. 2010-08-27: Core agrees with the estimated release date, and requests the date of the initial report of the vulnerability. 2010-09-09: After two weeks with no replies, Core again requests the date of the initial report of the vulnerability, and asks if the release of the fix is still on track for the end of September. 2010-09-16: Vendor replies that they will not be able to release fixes before the end of the year, as they have to correct third-party code by themselves. 2010-09-21: Core requests confirmation that the vendor won't release a fix before the end of the year. 2010-09-22: Vendor confirms that they won't be able to release fixes until the end of the year, as fixing third-party code is taking time. However, the vendor explains that current versions of the product have the vulnerable functionality disabled, that old versions of the product do not install the vulnerable functionality by default, and that installation of this functionality is not recommended. 2010-10-05: Core requests version numbers for vulnerable and non-vulnerable versions of the software, and asks if vulnerable users can update to a non-vulnerable version. 2010-09-06: Vendor replies with the version numbers and confirms that vulnerable users have to wait for the patch. 2010-10-07: Core decides to push the release date forward and wait for the release of the patch. 2010-10-22: Core asks Symantec for a precise release date for the fixes, and explains that the publication of the advisory won't be pushed further than December 2010. 2010-10-23: Vendor replies that the last known date was during December, and that they will confirm a firmer date. 2010-11-01: Core asks Symantec if a firmer release date has been confirmed. 2010-11-03: Vendor replies that the engineering team has not confirmed a release date, and asks if Core can hold the publication of the advisory until the end of the year. 2010-11-25: Core replies that the December 13th release date is fixed, and requests an update on the status of the patches. 2010-12-13: No update received, advisory CORE-2010-0728 is published.
-
References
-
About CoreLabs
CoreLabs, the research center of Core Security Technologies, is charged with anticipating the future needs and requirements for information security technologies. We conduct our research in several important areas of computer security including system vulnerabilities, cyber attack planning and simulation, source code auditing, and cryptography. Our results include problem formalization, identification of vulnerabilities, novel solutions and prototypes for new technologies. CoreLabs regularly publishes security advisories, technical papers, project information and shared software tools for public use at: [http://corelabs.coresecurity.com].
- About Core Security Technologies
Core Security Technologies develops strategic solutions that help security-conscious organizations worldwide develop and maintain a proactive process for securing their networks. The company's flagship product, CORE IMPACT, is the most comprehensive product for performing enterprise security assurance testing. CORE IMPACT evaluates network, endpoint and end-user vulnerabilities and identifies what resources are exposed. It enables organizations to determine if current security investments are detecting and preventing attacks. Core Security Technologies augments its leading technology solution with world-class security consulting services, including penetration testing and software security auditing. Based in Boston, MA and Buenos Aires, Argentina, Core Security Technologies can be reached at 617-399-6980 or on the Web at [http://www.coresecurity.com].
- Disclaimer
The contents of this advisory are copyright (c) 2010 Core Security Technologies and (c) 2010 CoreLabs, and are licensed under a Creative Commons Attribution Non-Commercial Share-Alike 3.0 (United States) License: [http://creativecommons.org/licenses/by-nc-sa/3.0/us/].
- PGP/GPG Keys
This advisory has been signed with the GPG key of Core Security Technologies advisories team, which is available for download at [http://www.coresecurity.com/files/attachments/core_security_advisories.asc]. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0GR4UACgkQyNibggitWa1iKQCfYtzFZOnNGpclzNZEDrwM08wr gwsAn2UYlqC0+IpliLAVTn/ItK4Sc3ne =Up/o -----END PGP SIGNATURE----- .
SOLUTION: Restrict access to trusted hosts only (e.g. via network access control lists). ----------------------------------------------------------------------
Secure your corporate defenses and reduce complexity in handling vulnerability threats with the new Secunia Vulnerability Intelligence Manager (VIM).
Request a free trial: http://secunia.com/products/corporate/vim/
TITLE: Symantec Products Intel Alert Management System Multiple Vulnerabilities
SECUNIA ADVISORY ID: SA43099
VERIFY ADVISORY: Secunia.com http://secunia.com/advisories/43099/ Customer Area (Credentials Required) https://ca.secunia.com/?page=viewadvisory&vuln_id=43099
RELEASE DATE: 2011-01-27
DISCUSS ADVISORY: http://secunia.com/advisories/43099/#comments
AVAILABLE ON SITE AND IN CUSTOMER AREA: * Last Update * Popularity * Comments * Criticality Level * Impact * Where * Solution Status * Operating System / Software * CVE Reference(s)
http://secunia.com/advisories/43099/
ONLY AVAILABLE IN CUSTOMER AREA: * Authentication Level * Report Reliability * Secunia PoC * Secunia Analysis * Systems Affected * Approve Distribution * Remediation Status * Secunia CVSS Score * CVSS
https://ca.secunia.com/?page=viewadvisory&vuln_id=43099
ONLY AVAILABLE WITH SECUNIA CSI AND SECUNIA PSI: * AUTOMATED SCANNING
http://secunia.com/vulnerability_scanning/personal/ http://secunia.com/vulnerability_scanning/corporate/wsus_sccm_3rd_third_party_patching/
DESCRIPTION: Multiple vulnerabilities have been reported in Symantec products, which can be exploited by malicious people to cause a DoS (Denial of Service) and compromise a vulnerable system.
1) An error in the Intel AMS2 component when processing certain messages can be exploited to cause a buffer overflow via specially crafted packets sent to TCP port 38292.
2) An error in the Intel AMS2 component when processing certain messages can be exploited to run arbitrary commands via specially crafted packets sent to TCP port 38292.
3) An error in the Intel AMS2 component when processing certain messages can be exploited to create arbitrary events (e.g. launch a program or send an email) via specially crafted messages sent to TCP port 38292.
Successful exploitation of the vulnerabilities may allow execution of arbitrary code. * Symantec System Center 10.x
SOLUTION: Update to version 10.1 MR10. * An anonymous researcher via ZDI. * Jorge Lucangeli Obes, CORE Security.
ORIGINAL ADVISORY: http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&suid=20110126_00 http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&suid=20110126_01
OTHER REFERENCES: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
DEEP LINKS: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
EXTENDED DESCRIPTION: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
EXTENDED SOLUTION: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
EXPLOIT: Further details available in Customer Area: http://secunia.com/products/corporate/EVM/
About: This Advisory was delivered by Secunia as a free service to help private users keeping their systems up to date against the latest vulnerabilities.
Subscribe: http://secunia.com/advisories/secunia_security_advisories/
Definitions: (Criticality, Where etc.) http://secunia.com/advisories/about_secunia_advisories/
Please Note: Secunia recommends that you verify all advisories you receive by clicking the link. Secunia NEVER sends attached files with advisories. Secunia does not advise people to install third party patches, only use those supplied by the vendor.
Unsubscribe: Secunia Security Advisories http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org
Show details on source website
{
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
"affected_products": {
"@id": "https://www.variotdbs.pl/ref/affected_products"
},
"configurations": {
"@id": "https://www.variotdbs.pl/ref/configurations"
},
"credits": {
"@id": "https://www.variotdbs.pl/ref/credits"
},
"cvss": {
"@id": "https://www.variotdbs.pl/ref/cvss/"
},
"description": {
"@id": "https://www.variotdbs.pl/ref/description/"
},
"exploit_availability": {
"@id": "https://www.variotdbs.pl/ref/exploit_availability/"
},
"external_ids": {
"@id": "https://www.variotdbs.pl/ref/external_ids/"
},
"iot": {
"@id": "https://www.variotdbs.pl/ref/iot/"
},
"iot_taxonomy": {
"@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
},
"patch": {
"@id": "https://www.variotdbs.pl/ref/patch/"
},
"problemtype_data": {
"@id": "https://www.variotdbs.pl/ref/problemtype_data/"
},
"references": {
"@id": "https://www.variotdbs.pl/ref/references/"
},
"sources": {
"@id": "https://www.variotdbs.pl/ref/sources/"
},
"sources_release_date": {
"@id": "https://www.variotdbs.pl/ref/sources_release_date/"
},
"sources_update_date": {
"@id": "https://www.variotdbs.pl/ref/sources_update_date/"
},
"threat_type": {
"@id": "https://www.variotdbs.pl/ref/threat_type/"
},
"title": {
"@id": "https://www.variotdbs.pl/ref/title/"
},
"type": {
"@id": "https://www.variotdbs.pl/ref/type/"
}
},
"@id": "https://www.variotdbs.pl/vuln/VAR-201012-0127",
"affected_products": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/affected_products#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"model": "alert management system",
"scope": null,
"trust": 1.4,
"vendor": "intel",
"version": null
},
{
"model": "antivirus",
"scope": "eq",
"trust": 1.0,
"vendor": "symantec",
"version": "10.1.4.4010"
},
{
"model": "alert management system",
"scope": "eq",
"trust": 1.0,
"vendor": "intel",
"version": "*"
},
{
"model": "endpoint protection",
"scope": "eq",
"trust": 1.0,
"vendor": "symantec",
"version": "11.0.2"
},
{
"model": "endpoint protection",
"scope": "eq",
"trust": 1.0,
"vendor": "symantec",
"version": "11.0"
},
{
"model": "endpoint protection",
"scope": "eq",
"trust": 1.0,
"vendor": "symantec",
"version": "11.0.4"
},
{
"model": "endpoint protection",
"scope": "eq",
"trust": 1.0,
"vendor": "symantec",
"version": "11.0.3001"
},
{
"model": "endpoint protection",
"scope": "eq",
"trust": 1.0,
"vendor": "symantec",
"version": "11.0.1"
},
{
"model": "antivirus",
"scope": "eq",
"trust": 0.8,
"vendor": "symantec",
"version": "windows 2000 sp4 edition corporate edition 10.1.4.4010"
},
{
"model": "endpoint protection",
"scope": "lt",
"trust": 0.8,
"vendor": "symantec",
"version": "11.x"
},
{
"model": "antivirus corporate edition",
"scope": "eq",
"trust": 0.3,
"vendor": "symantec",
"version": "10.1.4.4010"
}
],
"sources": [
{
"db": "BID",
"id": "45368"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"db": "NVD",
"id": "CVE-2010-3268"
},
{
"db": "CNNVD",
"id": "CNNVD-201012-180"
}
]
},
"configurations": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/configurations#",
"children": {
"@container": "@list"
},
"cpe_match": {
"@container": "@list"
},
"data": {
"@container": "@list"
},
"nodes": {
"@container": "@list"
}
},
"data": [
{
"CVE_data_version": "4.0",
"nodes": [
{
"children": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:intel:intel_alert_management_system:*:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
}
],
"operator": "OR"
},
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:o:microsoft:windows_2000:-:sp4:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": false
},
{
"cpe23Uri": "cpe:2.3:a:symantec:antivirus:10.1.4.4010:*:corporate:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
}
],
"operator": "OR"
}
],
"cpe_match": [],
"operator": "AND"
},
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.1:mp1:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.1:mp2:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.4:mp2:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0:ru5:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.2:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.2:mp1:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0:ru6:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0:ru6a:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0:rtm:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.2:mp2:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.3001:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0:ru6mp1:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0:ru6mp2:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.1:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.4:*:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:symantec:endpoint_protection:11.0.4:mp1a:*:*:*:*:*:*",
"cpe_name": [],
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "NVD",
"id": "CVE-2010-3268"
}
]
},
"credits": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/credits#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Nahuel Riva from Core Security Technologies",
"sources": [
{
"db": "BID",
"id": "45368"
}
],
"trust": 0.3
},
"cve": "CVE-2010-3268",
"cvss": {
"@context": {
"cvssV2": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
},
"cvssV3": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
},
"severity": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/cvss/severity#"
},
"@id": "https://www.variotdbs.pl/ref/cvss/severity"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
},
"@id": "https://www.variotdbs.pl/ref/sources"
}
},
"data": [
{
"cvssV2": [
{
"acInsufInfo": false,
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "NVD",
"availabilityImpact": "PARTIAL",
"baseScore": 5.0,
"confidentialityImpact": "NONE",
"exploitabilityScore": 10.0,
"impactScore": 2.9,
"integrityImpact": "NONE",
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"severity": "MEDIUM",
"trust": 1.0,
"userInteractionRequired": false,
"vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
"version": "2.0"
},
{
"acInsufInfo": null,
"accessComplexity": "Low",
"accessVector": "Network",
"authentication": "None",
"author": "NVD",
"availabilityImpact": "Partial",
"baseScore": 5.0,
"confidentialityImpact": "None",
"exploitabilityScore": null,
"id": "CVE-2010-3268",
"impactScore": null,
"integrityImpact": "None",
"obtainAllPrivilege": null,
"obtainOtherPrivilege": null,
"obtainUserPrivilege": null,
"severity": "Medium",
"trust": 0.8,
"userInteractionRequired": null,
"vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
"version": "2.0"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "PARTIAL",
"baseScore": 5.0,
"confidentialityImpact": "NONE",
"exploitabilityScore": 10.0,
"id": "VHN-45873",
"impactScore": 2.9,
"integrityImpact": "NONE",
"severity": "MEDIUM",
"trust": 0.1,
"vectorString": "AV:N/AC:L/AU:N/C:N/I:N/A:P",
"version": "2.0"
}
],
"cvssV3": [],
"severity": [
{
"author": "NVD",
"id": "CVE-2010-3268",
"trust": 1.8,
"value": "MEDIUM"
},
{
"author": "CNNVD",
"id": "CNNVD-201012-180",
"trust": 0.6,
"value": "MEDIUM"
},
{
"author": "VULHUB",
"id": "VHN-45873",
"trust": 0.1,
"value": "MEDIUM"
}
]
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-45873"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"db": "NVD",
"id": "CVE-2010-3268"
},
{
"db": "CNNVD",
"id": "CNNVD-201012-180"
}
]
},
"description": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/description#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "The GetStringAMSHandler function in prgxhndl.dll in hndlrsvc.exe in the Intel Alert Handler service (aka Symantec Intel Handler service) in Intel Alert Management System (AMS), as used in Symantec Antivirus Corporate Edition 10.1.4.4010 on Windows 2000 SP4 and Symantec Endpoint Protection before 11.x, does not properly validate the CommandLine field of an AMS request, which allows remote attackers to cause a denial of service (application crash) via a crafted request. Symantec Antivirus is prone to a remote denial-of-service vulnerability. \nAn attacker can exploit this issue to crash the affected application, denying service to legitimate users. \nSymantec Antivirus Corporate Edition 10.1.4.4010 is vulnerable; other versions may also be affected. -----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\n Core Security Technologies - CoreLabs Advisory\n http://corelabs.coresecurity.com/\n\nSymantec Intel Handler Service Remote DoS\n\n\n\n1. *Advisory Information*\n\nTitle: Symantec Intel Handler Service Remote DoS\nAdvisory Id: CORE-2010-0728\nAdvisory URL:\n[http://www.coresecurity.com/content/symantec-intel-handler-service-remote-dos]\n\nDate published: 2010-12-13\nDate of last update: 2010-12-13\nVendors contacted: Symantec\nRelease mode: User release\n\n\n\n2. *Vulnerability Information*\n\nClass: Input validation error [CWE-20]\nImpact: Denial of service\nRemotely Exploitable: Yes\nLocally Exploitable: No\nCVE Name: CVE-2010-3268\nBugtraq ID: N/A\n\n\n\n3. A source address in\na \u0027MOV\u0027 instruction is calculated from values present in the request,\ncausing a remote denial-of-service. \n\n\n4. *Vulnerable packages*\n\n . Older versions are probably affected too, but they were not checked. \n\n\n5. *Non-vulnerable packages*\n\n\n\n\n6. During the SEP 11.x\nengineering phase SEP was rewritten so that it no longer uses Intel AMS\ncode. The installation of AMS is disabled by default for SEP versions\nthat include it. The only workaround is to disable Intel AMS. \n\n\n7. *Credits*\n\nThis vulnerability was discovered and researched by Nahuel Riva from\nCore Security Technologies. Publication was coordinated by Jorge\nLucangeli Obes. \n\n\n8. *Technical Description / Proof of Concept Code*\n\nThe request is handled in \u0027prgxhndl.dll\u0027, called from \u0027hndlsrvc.exe\u0027,\nmore specifically from function \u00270x501A105D\u0027:\n\n/-----\n 501A105D /. 55 PUSH EBP\n 501A105E |. 8BEC MOV EBP,ESP\n 501A1060 |. 81EC 60040000 SUB ESP,460\n 501A1066 |. 8D45 F4 LEA EAX,DWORD PTR SS:[EBP-C]\n 501A1069 |. 57 PUSH EDI\n 501A106A |. 50 PUSH EAX\n 501A106B |. 68 34301A50 PUSH prgxhndl.501A3034 ;\n ASCII \"CommandLine\"\n 501A1070 |. FF75 0C PUSH DWORD PTR SS:[EBP+C]\n 501A1073 |. 8BF9 MOV EDI,ECX\n 501A1075 |. FF75 08 PUSH DWORD PTR SS:[EBP+8]\n 501A1078 |. E8 33010000 CALL\n \u003cJMP.\u0026HNDLRSVC.#17_?GetString@AMSHandler@@QAEHPAXKPADPAPAD@Z\u003e\n\n- -----/\n Inside that function, \u0027GetStringAMSHandler()\u0027 is called to parse the\ncontent of the \u0027CommandLine\u0027 field present in the request. In turn,\n\u0027GetStringAMSHandler()\u0027 forwards the request to function \u0027AMSLIB.18\u0027\npresent in \u0027AMSLIB.dll\u0027, and this function ends up calling the function\nthat crashes, \u0027AMSGetPastParamList()\u0027, also in \u0027AMSLIB.dll\u0027:\n\n/-----\n 500733AE |. 8B45 E4 MOV EAX,DWORD PTR SS:[EBP-1C]\n 500733B1 |. 50 PUSH EAX\n ; /Arg1\n 500733B2 |. E8 54F3FFFF CALL AMSLIB.AMSGetPastParamList\n ; \\AMSGetPastParamList\n\n- -----/\n The crash occurs at address \u00270x5007278B\u0027:\n\n/-----\n 50072786 |. 8B45 F0 |MOV EAX,DWORD PTR SS:[EBP-10]\n 50072789 |. 33C9 |XOR ECX,ECX\n 5007278B |. 8A08 |MOV CL,BYTE PTR DS:[EAX]\n 5007278D |. 85C9 |TEST ECX,ECX\n 5007278F |. 75 16 |JNZ SHORT AMSLIB.500727A7\n\n- -----/\n When trying to read at the memory area pointed to by EAX, this value is\ninvalid and the service crashes. This part of the code is parsing\n(inside a loop) the argument passed in the \u0027CommandLine\u0027 parameter. It\nseems that in many parts of the loop the pointer that is loaded from\n\u0027[EBP-10]\u0027 is calculated from a value present in the request. \n\n\n9. *Report Timeline*\n\n. 2010-08-12:\nInitial notification sent to Symantec. 2010-08-19:\nGiven that there was no answer since the initial notification, Core\nrequests a confirmation of reception. 2010-08-19:\nVendor replies that the initial notification was not received. 2010-08-20:\nCore resends original advisory draft. 2010-08-20:\nVendor acknowledges reception of advisory draft. 2010-08-25:\nVendor replies that the issue looks like a duplicate of another one,\nalready planned to be fixed in a September/October timeframe. Vendor\nwill investigate further and give a definite reply. 2010-08-26:\nCore acknowledges this reply. 2010-08-26:\nVendor confirms that the issue is a duplicate, but will give credit to\nNahuel Riva as \"secondary finder\". Vendor asks to postpone the\npublication of the advisory until a fix is released. 2010-08-27:\nCore agrees to postpone the publication of the advisory, given that an\nestimate release date for the fix is provided. 2010-08-27:\nVendor replies with an estimated release date for the end of September. 2010-08-27:\nCore agrees with the estimated release date, and requests the date of\nthe initial report of the vulnerability. 2010-09-09:\nAfter two weeks with no replies, Core again requests the date of the\ninitial report of the vulnerability, and asks if the release of the fix\nis still on track for the end of September. 2010-09-16:\nVendor replies that they will not be able to release fixes before the\nend of the year, as they have to correct third-party code by themselves. 2010-09-21:\nCore requests confirmation that the vendor won\u0027t release a fix before\nthe end of the year. 2010-09-22:\nVendor confirms that they won\u0027t be able to release fixes until the end\nof the year, as fixing third-party code is taking time. However, the\nvendor explains that current versions of the product have the vulnerable\nfunctionality disabled, that old versions of the product do not install\nthe vulnerable functionality by default, and that installation of this\nfunctionality is not recommended. 2010-10-05:\nCore requests version numbers for vulnerable and non-vulnerable versions\nof the software, and asks if vulnerable users can update to a\nnon-vulnerable version. 2010-09-06:\nVendor replies with the version numbers and confirms that vulnerable\nusers have to wait for the patch. 2010-10-07:\nCore decides to push the release date forward and wait for the release\nof the patch. 2010-10-22:\nCore asks Symantec for a precise release date for the fixes, and\nexplains that the publication of the advisory won\u0027t be pushed further\nthan December 2010. 2010-10-23:\nVendor replies that the last known date was during December, and that\nthey will confirm a firmer date. 2010-11-01:\nCore asks Symantec if a firmer release date has been confirmed. 2010-11-03:\nVendor replies that the engineering team has not confirmed a release\ndate, and asks if Core can hold the publication of the advisory until\nthe end of the year. 2010-11-25:\nCore replies that the December 13th release date is fixed, and requests\nan update on the status of the patches. 2010-12-13:\nNo update received, advisory CORE-2010-0728 is published. \n\n\n\n10. *References*\n\n\n\n\n11. *About CoreLabs*\n\nCoreLabs, the research center of Core Security Technologies, is charged\nwith anticipating the future needs and requirements for information\nsecurity technologies. We conduct our research in several important\nareas of computer security including system vulnerabilities, cyber\nattack planning and simulation, source code auditing, and cryptography. \nOur results include problem formalization, identification of\nvulnerabilities, novel solutions and prototypes for new technologies. \nCoreLabs regularly publishes security advisories, technical papers,\nproject information and shared software tools for public use at:\n[http://corelabs.coresecurity.com]. \n\n\n12. *About Core Security Technologies*\n\nCore Security Technologies develops strategic solutions that help\nsecurity-conscious organizations worldwide develop and maintain a\nproactive process for securing their networks. The company\u0027s flagship\nproduct, CORE IMPACT, is the most comprehensive product for performing\nenterprise security assurance testing. CORE IMPACT evaluates network,\nendpoint and end-user vulnerabilities and identifies what resources are\nexposed. It enables organizations to determine if current security\ninvestments are detecting and preventing attacks. Core Security\nTechnologies augments its leading technology solution with world-class\nsecurity consulting services, including penetration testing and software\nsecurity auditing. Based in Boston, MA and Buenos Aires, Argentina, Core\nSecurity Technologies can be reached at 617-399-6980 or on the Web at\n[http://www.coresecurity.com]. \n\n\n13. *Disclaimer*\n\nThe contents of this advisory are copyright (c) 2010 Core Security\nTechnologies and (c) 2010 CoreLabs, and are licensed under a Creative\nCommons Attribution Non-Commercial Share-Alike 3.0 (United States)\nLicense: [http://creativecommons.org/licenses/by-nc-sa/3.0/us/]. \n\n\n14. *PGP/GPG Keys*\n\nThis advisory has been signed with the GPG key of Core Security\nTechnologies advisories team, which is available for download at\n[http://www.coresecurity.com/files/attachments/core_security_advisories.asc]. \n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.10 (GNU/Linux)\nComment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/\n\niEYEARECAAYFAk0GR4UACgkQyNibggitWa1iKQCfYtzFZOnNGpclzNZEDrwM08wr\ngwsAn2UYlqC0+IpliLAVTn/ItK4Sc3ne\n=Up/o\n-----END PGP SIGNATURE-----\n. \n\nSOLUTION:\nRestrict access to trusted hosts only (e.g. via network access\ncontrol lists). ----------------------------------------------------------------------\n\n\nSecure your corporate defenses and reduce complexity in handling vulnerability threats with the new Secunia Vulnerability Intelligence Manager (VIM). \n\nRequest a free trial: \nhttp://secunia.com/products/corporate/vim/\n\n\n----------------------------------------------------------------------\n\nTITLE:\nSymantec Products Intel Alert Management System Multiple\nVulnerabilities\n\nSECUNIA ADVISORY ID:\nSA43099\n\nVERIFY ADVISORY:\nSecunia.com\nhttp://secunia.com/advisories/43099/\nCustomer Area (Credentials Required)\nhttps://ca.secunia.com/?page=viewadvisory\u0026vuln_id=43099\n\nRELEASE DATE:\n2011-01-27\n\nDISCUSS ADVISORY:\nhttp://secunia.com/advisories/43099/#comments\n\nAVAILABLE ON SITE AND IN CUSTOMER AREA:\n * Last Update\n * Popularity\n * Comments\n * Criticality Level\n * Impact\n * Where\n * Solution Status\n * Operating System / Software\n * CVE Reference(s)\n\nhttp://secunia.com/advisories/43099/\n\nONLY AVAILABLE IN CUSTOMER AREA:\n * Authentication Level\n * Report Reliability\n * Secunia PoC\n * Secunia Analysis\n * Systems Affected\n * Approve Distribution\n * Remediation Status\n * Secunia CVSS Score\n * CVSS\n\nhttps://ca.secunia.com/?page=viewadvisory\u0026vuln_id=43099\n\nONLY AVAILABLE WITH SECUNIA CSI AND SECUNIA PSI:\n * AUTOMATED SCANNING\n\nhttp://secunia.com/vulnerability_scanning/personal/\nhttp://secunia.com/vulnerability_scanning/corporate/wsus_sccm_3rd_third_party_patching/\n\nDESCRIPTION:\nMultiple vulnerabilities have been reported in Symantec products,\nwhich can be exploited by malicious people to cause a DoS (Denial of\nService) and compromise a vulnerable system. \n\n1) An error in the Intel AMS2 component when processing certain\nmessages can be exploited to cause a buffer overflow via specially\ncrafted packets sent to TCP port 38292. \n\n2) An error in the Intel AMS2 component when processing certain\nmessages can be exploited to run arbitrary commands via specially\ncrafted packets sent to TCP port 38292. \n\n3) An error in the Intel AMS2 component when processing certain\nmessages can be exploited to create arbitrary events (e.g. launch a\nprogram or send an email) via specially crafted messages sent to TCP\nport 38292. \n\nSuccessful exploitation of the vulnerabilities may allow execution of\narbitrary code. \n* Symantec System Center 10.x\n\nSOLUTION:\nUpdate to version 10.1 MR10. \n* An anonymous researcher via ZDI. \n* Jorge Lucangeli Obes, CORE Security. \n\nORIGINAL ADVISORY:\nhttp://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026suid=20110126_00\nhttp://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026suid=20110126_01\n\nOTHER REFERENCES:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nDEEP LINKS:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nEXTENDED DESCRIPTION:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nEXTENDED SOLUTION:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\nEXPLOIT:\nFurther details available in Customer Area:\nhttp://secunia.com/products/corporate/EVM/\n\n----------------------------------------------------------------------\n\nAbout:\nThis Advisory was delivered by Secunia as a free service to help\nprivate users keeping their systems up to date against the latest\nvulnerabilities. \n\nSubscribe:\nhttp://secunia.com/advisories/secunia_security_advisories/\n\nDefinitions: (Criticality, Where etc.)\nhttp://secunia.com/advisories/about_secunia_advisories/\n\n\nPlease Note:\nSecunia recommends that you verify all advisories you receive by\nclicking the link. \nSecunia NEVER sends attached files with advisories. \nSecunia does not advise people to install third party patches, only\nuse those supplied by the vendor. \n\n----------------------------------------------------------------------\n\nUnsubscribe: Secunia Security Advisories\nhttp://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org\n\n----------------------------------------------------------------------\n\n\n",
"sources": [
{
"db": "NVD",
"id": "CVE-2010-3268"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"db": "BID",
"id": "45368"
},
{
"db": "VULHUB",
"id": "VHN-45873"
},
{
"db": "PACKETSTORM",
"id": "96673"
},
{
"db": "PACKETSTORM",
"id": "96852"
},
{
"db": "PACKETSTORM",
"id": "97932"
}
],
"trust": 2.25
},
"exploit_availability": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/exploit_availability#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"reference": "https://www.scap.org.cn/vuln/vhn-45873",
"trust": 0.1,
"type": "unknown"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-45873"
}
]
},
"external_ids": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/external_ids#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"db": "NVD",
"id": "CVE-2010-3268",
"trust": 2.9
},
{
"db": "SECUNIA",
"id": "42593",
"trust": 1.2
},
{
"db": "SECUNIA",
"id": "43099",
"trust": 1.2
},
{
"db": "BID",
"id": "45936",
"trust": 1.1
},
{
"db": "VUPEN",
"id": "ADV-2010-3206",
"trust": 1.1
},
{
"db": "VUPEN",
"id": "ADV-2011-0234",
"trust": 1.1
},
{
"db": "SECTRACK",
"id": "1024866",
"trust": 1.1
},
{
"db": "JVNDB",
"id": "JVNDB-2010-003041",
"trust": 0.8
},
{
"db": "CNNVD",
"id": "CNNVD-201012-180",
"trust": 0.7
},
{
"db": "BID",
"id": "45368",
"trust": 0.4
},
{
"db": "PACKETSTORM",
"id": "96673",
"trust": 0.2
},
{
"db": "VULHUB",
"id": "VHN-45873",
"trust": 0.1
},
{
"db": "PACKETSTORM",
"id": "96852",
"trust": 0.1
},
{
"db": "PACKETSTORM",
"id": "97932",
"trust": 0.1
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-45873"
},
{
"db": "BID",
"id": "45368"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"db": "PACKETSTORM",
"id": "96673"
},
{
"db": "PACKETSTORM",
"id": "96852"
},
{
"db": "PACKETSTORM",
"id": "97932"
},
{
"db": "NVD",
"id": "CVE-2010-3268"
},
{
"db": "CNNVD",
"id": "CNNVD-201012-180"
}
]
},
"id": "VAR-201012-0127",
"iot": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/iot#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": true,
"sources": [
{
"db": "VULHUB",
"id": "VHN-45873"
}
],
"trust": 0.01
},
"last_update_date": "2023-12-18T10:43:57.547000Z",
"patch": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/patch#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"title": "Top Page",
"trust": 0.8,
"url": "http://www.intel.com/"
},
{
"title": "symantec securityupdates sid 20110126_00",
"trust": 0.8,
"url": "http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026year=2011\u0026suid=20110126_00"
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
}
]
},
"problemtype_data": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"problemtype": "CWE-20",
"trust": 1.9
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-45873"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"db": "NVD",
"id": "CVE-2010-3268"
}
]
},
"references": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/references#",
"data": {
"@container": "@list"
},
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": [
{
"trust": 1.2,
"url": "http://www.coresecurity.com/content/symantec-intel-handler-service-remote-dos"
},
{
"trust": 1.1,
"url": "http://www.securityfocus.com/bid/45936"
},
{
"trust": 1.1,
"url": "http://www.securityfocus.com/archive/1/515191/100/0/threaded"
},
{
"trust": 1.1,
"url": "http://www.securitytracker.com/id?1024866"
},
{
"trust": 1.1,
"url": "http://secunia.com/advisories/42593"
},
{
"trust": 1.1,
"url": "http://secunia.com/advisories/43099"
},
{
"trust": 1.1,
"url": "http://www.vupen.com/english/advisories/2010/3206"
},
{
"trust": 1.1,
"url": "http://www.vupen.com/english/advisories/2011/0234"
},
{
"trust": 1.1,
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/64028"
},
{
"trust": 1.0,
"url": "http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026year=2011\u0026suid=20110126_00"
},
{
"trust": 0.8,
"url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-3268"
},
{
"trust": 0.8,
"url": "http://web.nvd.nist.gov/view/vuln/detail?vulnid=cve-2010-3268"
},
{
"trust": 0.4,
"url": "http://www.coresecurity.com/content/symantec-intel-handler-service-remote-dos]"
},
{
"trust": 0.3,
"url": "http://www.symantec.com"
},
{
"trust": 0.2,
"url": "http://secunia.com/products/corporate/evm/"
},
{
"trust": 0.2,
"url": "http://secunia.com/advisories/secunia_security_advisories/"
},
{
"trust": 0.2,
"url": "http://secunia.com/vulnerability_scanning/corporate/wsus_sccm_3rd_third_party_patching/"
},
{
"trust": 0.2,
"url": "http://secunia.com/products/corporate/vim/"
},
{
"trust": 0.2,
"url": "http://secunia.com/vulnerability_scanning/personal/"
},
{
"trust": 0.2,
"url": "http://secunia.com/sec_adv_unsubscribe/?email=packet%40packetstormsecurity.org"
},
{
"trust": 0.2,
"url": "http://secunia.com/advisories/about_secunia_advisories/"
},
{
"trust": 0.1,
"url": "http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026amp;pvid=security_advisory\u0026amp;year=2011\u0026amp;suid=20110126_00"
},
{
"trust": 0.1,
"url": "http://corelabs.coresecurity.com]."
},
{
"trust": 0.1,
"url": "http://www.coresecurity.com/files/attachments/core_security_advisories.asc]."
},
{
"trust": 0.1,
"url": "http://enigmail.mozdev.org/"
},
{
"trust": 0.1,
"url": "http://corelabs.coresecurity.com/"
},
{
"trust": 0.1,
"url": "http://www.coresecurity.com]."
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2010-3268"
},
{
"trust": 0.1,
"url": "http://creativecommons.org/licenses/by-nc-sa/3.0/us/]."
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/42593/"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/42593/#comments"
},
{
"trust": 0.1,
"url": "https://ca.secunia.com/?page=viewadvisory\u0026vuln_id=42593"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/43099/"
},
{
"trust": 0.1,
"url": "http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026suid=20110126_01"
},
{
"trust": 0.1,
"url": "http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026suid=20110126_00"
},
{
"trust": 0.1,
"url": "http://secunia.com/advisories/43099/#comments"
},
{
"trust": 0.1,
"url": "https://ca.secunia.com/?page=viewadvisory\u0026vuln_id=43099"
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-45873"
},
{
"db": "BID",
"id": "45368"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"db": "PACKETSTORM",
"id": "96673"
},
{
"db": "PACKETSTORM",
"id": "96852"
},
{
"db": "PACKETSTORM",
"id": "97932"
},
{
"db": "NVD",
"id": "CVE-2010-3268"
}
]
},
"sources": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#",
"data": {
"@container": "@list"
}
},
"data": [
{
"db": "VULHUB",
"id": "VHN-45873"
},
{
"db": "BID",
"id": "45368"
},
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"db": "PACKETSTORM",
"id": "96673"
},
{
"db": "PACKETSTORM",
"id": "96852"
},
{
"db": "PACKETSTORM",
"id": "97932"
},
{
"db": "NVD",
"id": "CVE-2010-3268"
},
{
"db": "CNNVD",
"id": "CNNVD-201012-180"
}
]
},
"sources_release_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2010-12-22T00:00:00",
"db": "VULHUB",
"id": "VHN-45873"
},
{
"date": "2010-12-13T00:00:00",
"db": "BID",
"id": "45368"
},
{
"date": "2012-03-27T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"date": "2010-12-13T13:19:27",
"db": "PACKETSTORM",
"id": "96673"
},
{
"date": "2010-12-21T09:42:08",
"db": "PACKETSTORM",
"id": "96852"
},
{
"date": "2011-01-27T05:49:51",
"db": "PACKETSTORM",
"id": "97932"
},
{
"date": "2010-12-22T21:00:15.723000",
"db": "NVD",
"id": "CVE-2010-3268"
},
{
"date": "2010-12-20T00:00:00",
"db": "CNNVD",
"id": "CNNVD-201012-180"
}
]
},
"sources_update_date": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
"data": {
"@container": "@list"
}
},
"data": [
{
"date": "2018-10-30T00:00:00",
"db": "VULHUB",
"id": "VHN-45873"
},
{
"date": "2010-12-13T00:00:00",
"db": "BID",
"id": "45368"
},
{
"date": "2012-03-27T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2010-003041"
},
{
"date": "2018-10-30T16:25:57.450000",
"db": "NVD",
"id": "CVE-2010-3268"
},
{
"date": "2010-12-23T00:00:00",
"db": "CNNVD",
"id": "CNNVD-201012-180"
}
]
},
"threat_type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/threat_type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "remote",
"sources": [
{
"db": "PACKETSTORM",
"id": "96673"
},
{
"db": "CNNVD",
"id": "CNNVD-201012-180"
}
],
"trust": 0.7
},
"title": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/title#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "Symantec Antivirus Corporate Edition Used in etc. Intel AMS of GetStringAMSHandler Service disruption in functions (DoS) Vulnerabilities",
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2010-003041"
}
],
"trust": 0.8
},
"type": {
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/type#",
"sources": {
"@container": "@list",
"@context": {
"@vocab": "https://www.variotdbs.pl/ref/sources#"
}
}
},
"data": "input validation",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-201012-180"
}
],
"trust": 0.6
}
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.