JVNDB-2007-000135
Vulnerability from jvndb - Published: 2008-05-20 15:00 - Updated:2008-05-20 15:00| Vendor | Product | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||
{
"@rdf:about": "https://jvndb.jvn.jp/en/contents/2007/JVNDB-2007-000135.html",
"dc:date": "2008-05-21T00:00+09:00",
"dcterms:issued": "2008-05-21T00:00+09:00",
"dcterms:modified": "2008-05-21T00:00+09:00",
"description": "CCC Cleaner, provided by Cyber Clean Center between January 25 and February 9, 2007, contains a buffer overflow vulnerability that occurs when it scans UPX-packed executables.\r\n\r\nThis vulnerability is caused by a buffer overflow vulnerability in the scan processing of UPX compressed executables found in TrendMicro Antivirus. For details of this vulnerability, please refer to TrendMicro\u0027s website.\r\n\r\nCCC Cleaner is affected by this vulnerability only when the following file is contained in the \"CCC Cleaner\" folder.\r\n\r\nFilenames: lpt$vpn.185\r\n\r\nAs of February 13, 2006, Trend Micro has announced that the vulnerability \"the Anti-Rootkit Common Module (TmComm.sys)\" disclosed on February 11, 2006 does not affect CCC Cleaner. For more information, refer to the vendor\u0027s website.",
"link": "https://jvndb.jvn.jp/en/contents/2007/JVNDB-2007-000135.html",
"sec:cpe": [
{
"#text": "cpe:/a:misc:ccc_cleaner",
"@product": "CCC Cleaner",
"@vendor": "Cyber Clean Center",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:anti-spyware_for_consumer",
"@product": "Trend Micro Anti-Spyware for Consumer",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:anti-spyware_for_enterprise",
"@product": "Trend Micro Anti-Spyware for Enterprise",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:anti-spyware_for_smb",
"@product": "Trend Micro Anti-Spyware for SMB",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:antivirus",
"@product": "Trend Micro Antivirus",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:business_security",
"@product": "Worry-Free Business Security",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:client_server_messaging_security_for_smb",
"@product": "Client / Server / Messaging Security for SMB",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:damage_cleanup_services",
"@product": "Damage Cleanup Services",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:pc_cillin_internet_security",
"@product": "Trend Micro PC Cillin Internet Security",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:rootkit_provision_module_tmcomm.sys",
"@product": "Rootkit Provision Module (TmComm.sys)",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:trendmicro:virus_baster",
"@product": "Virus Baster",
"@vendor": "Trend Micro, Inc.",
"@version": "2.2"
}
],
"sec:cvss": {
"@score": "5.4",
"@severity": "Medium",
"@type": "Base",
"@vector": "AV:N/AC:H/Au:N/C:N/I:N/A:C",
"@version": "2.0"
},
"sec:identifier": "JVNDB-2007-000135",
"sec:references": [
{
"#text": "http://jvn.jp/en/jp/JVN77366274/index.html",
"@id": "JVN#77366274",
"@source": "JVN"
},
{
"#text": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0856",
"@id": "CVE-2007-0856",
"@source": "CVE"
},
{
"#text": "http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-0856",
"@id": "CVE-2007-0856",
"@source": "NVD"
},
{
"#text": "http://www.kb.cert.org/vuls/id/282240",
"@id": "VU#282240",
"@source": "CERT-VN"
},
{
"#text": "http://www.kb.cert.org/vuls/id/666800",
"@id": "VU#666800",
"@source": "CERT-VN"
},
{
"#text": "http://secunia.com/advisories/24069/",
"@id": "SA24069",
"@source": "SECUNIA"
},
{
"#text": "http://www.securityfocus.com/bid/22448",
"@id": "22448",
"@source": "BID"
},
{
"#text": "http://xforce.iss.net/xforce/xfdb/32353",
"@id": "32353",
"@source": "XF"
},
{
"#text": "http://www.securitytracker.com/id?1017604",
"@id": "1017604",
"@source": "SECTRACK"
},
{
"#text": "http://www.securitytracker.com/id?1017605",
"@id": "1017605",
"@source": "SECTRACK"
},
{
"#text": "http://www.securitytracker.com/id?1017606",
"@id": "1017606",
"@source": "SECTRACK"
},
{
"#text": "http://www.frsirt.com/english/advisories/2007/0521",
"@id": "FrSIRT/ADV-2007-0521",
"@source": "FRSIRT"
}
],
"title": "CCC Cleaner buffer overflow vulnerability"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.