VAR-201907-1078
Vulnerability from variot - Updated: 2024-11-23 21:59Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices have default credentials that are hardcoded in the firmware and can be extracted by anyone who reverses the firmware to identify them. If the firmware version V2.420.AC00.16.R 9/9/2016 is dissected using binwalk tool, one obtains a _user-x.squashfs.img.extracted archive which contains the filesystem set up on the device that many of the binaries in the /usr folder. The binary "sonia" is the one that has the vulnerable function that sets up the default credentials on the device. If one opens this binary in IDA-pro, one will notice that this follows a ARM little endian format. The function sub_3DB2FC in IDA pro is identified to be setting up the values at address 0x003DB5A6. The sub_5C057C then sets this value and adds it to the Configuration files in /mnt/mtd/Config/Account1 file. Amcrest IPM-721S The device contains a vulnerability related to the use of hard-coded credentials.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. The Amcrest IPM-721S is a wireless IP camera from Amcrest. An authorization issue vulnerability exists in the AmcrestIPM-721SV2.420.AC00.16.R.20160909 release. The vulnerability stems from a lack of authentication in the network system or product or insufficient strength of authentication. No detailed vulnerability details are currently available. There is a trust management vulnerability in Amcrest IPM-721S V2.420.AC00.16.R.20160909. Attackers can use default passwords or hard-coded passwords, hard-coded certificates, etc. to attack affected components
Show details on source website{
"affected_products": {
"_id": null,
"data": [
{
"_id": null,
"model": "ipm-721s",
"scope": "lte",
"trust": 1.0,
"vendor": "amcrest",
"version": "2.420.ac00.16.r.20160909"
},
{
"_id": null,
"model": "ipm-721s",
"scope": "eq",
"trust": 0.8,
"vendor": "amcrest",
"version": "2.420.ac00.16.r.20160909"
},
{
"_id": null,
"model": "ipm-721s v2.420.ac00.16.r.20160909",
"scope": null,
"trust": 0.6,
"vendor": "amcrest",
"version": null
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2019-24192"
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
},
{
"db": "NVD",
"id": "CVE-2017-8226"
}
]
},
"configurations": {
"_id": null,
"data": [
{
"CVE_data_version": "4.0",
"nodes": [
{
"cpe_match": [
{
"cpe22Uri": "cpe:/o:amcrest:ipm-721s_firmware",
"vulnerable": true
}
],
"operator": "OR"
}
]
}
],
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
}
]
},
"credits": {
"_id": null,
"data": "Mandar Satam",
"sources": [
{
"db": "PACKETSTORM",
"id": "153224"
}
],
"trust": 0.1
},
"cve": "CVE-2017-8226",
"cvss": {
"_id": null,
"data": [
{
"cvssV2": [
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "nvd@nist.gov",
"availabilityImpact": "PARTIAL",
"baseScore": 7.5,
"confidentialityImpact": "PARTIAL",
"exploitabilityScore": 10.0,
"id": "CVE-2017-8226",
"impactScore": 6.4,
"integrityImpact": "PARTIAL",
"severity": "HIGH",
"trust": 1.9,
"vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P",
"version": "2.0"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "CNVD",
"availabilityImpact": "PARTIAL",
"baseScore": 7.5,
"confidentialityImpact": "PARTIAL",
"exploitabilityScore": 10.0,
"id": "CNVD-2019-24192",
"impactScore": 6.4,
"integrityImpact": "PARTIAL",
"severity": "HIGH",
"trust": 0.6,
"vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P",
"version": "2.0"
},
{
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"author": "VULHUB",
"availabilityImpact": "PARTIAL",
"baseScore": 7.5,
"confidentialityImpact": "PARTIAL",
"exploitabilityScore": 10.0,
"id": "VHN-116429",
"impactScore": 6.4,
"integrityImpact": "PARTIAL",
"severity": "HIGH",
"trust": 0.1,
"vectorString": "AV:N/AC:L/AU:N/C:P/I:P/A:P",
"version": "2.0"
}
],
"cvssV3": [
{
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"author": "nvd@nist.gov",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"exploitabilityScore": 3.9,
"id": "CVE-2017-8226",
"impactScore": 5.9,
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"trust": 1.8,
"userInteraction": "NONE",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.0"
}
],
"severity": [
{
"author": "nvd@nist.gov",
"id": "CVE-2017-8226",
"trust": 1.0,
"value": "CRITICAL"
},
{
"author": "NVD",
"id": "CVE-2017-8226",
"trust": 0.8,
"value": "Critical"
},
{
"author": "CNVD",
"id": "CNVD-2019-24192",
"trust": 0.6,
"value": "HIGH"
},
{
"author": "CNNVD",
"id": "CNNVD-201907-195",
"trust": 0.6,
"value": "CRITICAL"
},
{
"author": "VULHUB",
"id": "VHN-116429",
"trust": 0.1,
"value": "HIGH"
},
{
"author": "VULMON",
"id": "CVE-2017-8226",
"trust": 0.1,
"value": "HIGH"
}
]
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2019-24192"
},
{
"db": "VULHUB",
"id": "VHN-116429"
},
{
"db": "VULMON",
"id": "CVE-2017-8226"
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
},
{
"db": "CNNVD",
"id": "CNNVD-201907-195"
},
{
"db": "NVD",
"id": "CVE-2017-8226"
}
]
},
"description": {
"_id": null,
"data": "Amcrest IPM-721S V2.420.AC00.16.R.20160909 devices have default credentials that are hardcoded in the firmware and can be extracted by anyone who reverses the firmware to identify them. If the firmware version V2.420.AC00.16.R 9/9/2016 is dissected using binwalk tool, one obtains a _user-x.squashfs.img.extracted archive which contains the filesystem set up on the device that many of the binaries in the /usr folder. The binary \"sonia\" is the one that has the vulnerable function that sets up the default credentials on the device. If one opens this binary in IDA-pro, one will notice that this follows a ARM little endian format. The function sub_3DB2FC in IDA pro is identified to be setting up the values at address 0x003DB5A6. The sub_5C057C then sets this value and adds it to the Configuration files in /mnt/mtd/Config/Account1 file. Amcrest IPM-721S The device contains a vulnerability related to the use of hard-coded credentials.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. The Amcrest IPM-721S is a wireless IP camera from Amcrest. An authorization issue vulnerability exists in the AmcrestIPM-721SV2.420.AC00.16.R.20160909 release. The vulnerability stems from a lack of authentication in the network system or product or insufficient strength of authentication. No detailed vulnerability details are currently available. There is a trust management vulnerability in Amcrest IPM-721S V2.420.AC00.16.R.20160909. Attackers can use default passwords or hard-coded passwords, hard-coded certificates, etc. to attack affected components",
"sources": [
{
"db": "NVD",
"id": "CVE-2017-8226"
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
},
{
"db": "CNVD",
"id": "CNVD-2019-24192"
},
{
"db": "VULHUB",
"id": "VHN-116429"
},
{
"db": "VULMON",
"id": "CVE-2017-8226"
}
],
"trust": 2.34
},
"external_ids": {
"_id": null,
"data": [
{
"db": "NVD",
"id": "CVE-2017-8226",
"trust": 3.3
},
{
"db": "PACKETSTORM",
"id": "153224",
"trust": 1.9
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564",
"trust": 0.8
},
{
"db": "CNNVD",
"id": "CNNVD-201907-195",
"trust": 0.7
},
{
"db": "CNVD",
"id": "CNVD-2019-24192",
"trust": 0.6
},
{
"db": "VULHUB",
"id": "VHN-116429",
"trust": 0.1
},
{
"db": "VULMON",
"id": "CVE-2017-8226",
"trust": 0.1
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2019-24192"
},
{
"db": "VULHUB",
"id": "VHN-116429"
},
{
"db": "VULMON",
"id": "CVE-2017-8226"
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
},
{
"db": "PACKETSTORM",
"id": "153224"
},
{
"db": "CNNVD",
"id": "CNNVD-201907-195"
},
{
"db": "NVD",
"id": "CVE-2017-8226"
}
]
},
"id": "VAR-201907-1078",
"iot": {
"_id": null,
"data": true,
"sources": [
{
"db": "CNVD",
"id": "CNVD-2019-24192"
},
{
"db": "VULHUB",
"id": "VHN-116429"
}
],
"trust": 1.3470588399999999
},
"iot_taxonomy": {
"_id": null,
"data": [
{
"category": [
"Network device"
],
"sub_category": null,
"trust": 0.6
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2019-24192"
}
]
},
"last_update_date": "2024-11-23T21:59:49.499000Z",
"patch": {
"_id": null,
"data": [
{
"title": "Top Page",
"trust": 0.8,
"url": "https://amcrest.com/"
},
{
"title": "Patch for AmcrestIPM-721S Authorization Issue Vulnerability",
"trust": 0.6,
"url": "https://www.cnvd.org.cn/patchInfo/show/170539"
},
{
"title": "Amcrest IPM-721S Remediation measures for authorization problem vulnerabilities",
"trust": 0.6,
"url": "http://www.cnnvd.org.cn/web/xxk/bdxqById.tag?id=94390"
},
{
"title": "IoT_vulnerabilities",
"trust": 0.1,
"url": "https://github.com/ethanhunnt/IoT_vulnerabilities "
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2019-24192"
},
{
"db": "VULMON",
"id": "CVE-2017-8226"
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
},
{
"db": "CNNVD",
"id": "CNNVD-201907-195"
}
]
},
"problemtype_data": {
"_id": null,
"data": [
{
"problemtype": "CWE-798",
"trust": 1.9
}
],
"sources": [
{
"db": "VULHUB",
"id": "VHN-116429"
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
},
{
"db": "NVD",
"id": "CVE-2017-8226"
}
]
},
"references": {
"_id": null,
"data": [
{
"trust": 2.6,
"url": "https://github.com/ethanhunnt/iot_vulnerabilities/blob/master/amcrest_sec_issues.pdf"
},
{
"trust": 2.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2017-8226"
},
{
"trust": 1.8,
"url": "https://seclists.org/bugtraq/2019/jun/8"
},
{
"trust": 1.8,
"url": "http://packetstormsecurity.com/files/153224/amcrest-ipm-721s-credential-disclosure-privilege-escalation.html"
},
{
"trust": 0.8,
"url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2017-8226"
},
{
"trust": 0.1,
"url": "https://cwe.mitre.org/data/definitions/798.html"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov"
},
{
"trust": 0.1,
"url": "https://github.com/ethanhunnt/iot_vulnerabilities"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2017-8229"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2017-8227"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2017-8228"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2017-13719"
},
{
"trust": 0.1,
"url": "https://nvd.nist.gov/vuln/detail/cve-2017-8230"
}
],
"sources": [
{
"db": "CNVD",
"id": "CNVD-2019-24192"
},
{
"db": "VULHUB",
"id": "VHN-116429"
},
{
"db": "VULMON",
"id": "CVE-2017-8226"
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
},
{
"db": "PACKETSTORM",
"id": "153224"
},
{
"db": "CNNVD",
"id": "CNNVD-201907-195"
},
{
"db": "NVD",
"id": "CVE-2017-8226"
}
]
},
"sources": {
"_id": null,
"data": [
{
"db": "CNVD",
"id": "CNVD-2019-24192",
"ident": null
},
{
"db": "VULHUB",
"id": "VHN-116429",
"ident": null
},
{
"db": "VULMON",
"id": "CVE-2017-8226",
"ident": null
},
{
"db": "JVNDB",
"id": "JVNDB-2017-014564",
"ident": null
},
{
"db": "PACKETSTORM",
"id": "153224",
"ident": null
},
{
"db": "CNNVD",
"id": "CNNVD-201907-195",
"ident": null
},
{
"db": "NVD",
"id": "CVE-2017-8226",
"ident": null
}
]
},
"sources_release_date": {
"_id": null,
"data": [
{
"date": "2019-07-22T00:00:00",
"db": "CNVD",
"id": "CNVD-2019-24192",
"ident": null
},
{
"date": "2019-07-03T00:00:00",
"db": "VULHUB",
"id": "VHN-116429",
"ident": null
},
{
"date": "2019-07-03T00:00:00",
"db": "VULMON",
"id": "CVE-2017-8226",
"ident": null
},
{
"date": "2019-07-12T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2017-014564",
"ident": null
},
{
"date": "2019-06-07T15:06:02",
"db": "PACKETSTORM",
"id": "153224",
"ident": null
},
{
"date": "2019-07-03T00:00:00",
"db": "CNNVD",
"id": "CNNVD-201907-195",
"ident": null
},
{
"date": "2019-07-03T20:15:10.430000",
"db": "NVD",
"id": "CVE-2017-8226",
"ident": null
}
]
},
"sources_update_date": {
"_id": null,
"data": [
{
"date": "2019-07-24T00:00:00",
"db": "CNVD",
"id": "CNVD-2019-24192",
"ident": null
},
{
"date": "2019-07-11T00:00:00",
"db": "VULHUB",
"id": "VHN-116429",
"ident": null
},
{
"date": "2019-07-11T00:00:00",
"db": "VULMON",
"id": "CVE-2017-8226",
"ident": null
},
{
"date": "2019-07-12T00:00:00",
"db": "JVNDB",
"id": "JVNDB-2017-014564",
"ident": null
},
{
"date": "2019-08-02T00:00:00",
"db": "CNNVD",
"id": "CNNVD-201907-195",
"ident": null
},
{
"date": "2024-11-21T03:33:34.810000",
"db": "NVD",
"id": "CVE-2017-8226",
"ident": null
}
]
},
"threat_type": {
"_id": null,
"data": "remote",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-201907-195"
}
],
"trust": 0.6
},
"title": {
"_id": null,
"data": "Amcrest IPM-721S Vulnerabilities related to the use of hard-coded credentials on devices",
"sources": [
{
"db": "JVNDB",
"id": "JVNDB-2017-014564"
}
],
"trust": 0.8
},
"type": {
"_id": null,
"data": "trust management problem",
"sources": [
{
"db": "CNNVD",
"id": "CNNVD-201907-195"
}
],
"trust": 0.6
}
}
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.