ObiHai ObiPhone 1032/ObiPhone 1062 prior 5.0.0 Build 3497 Header null termination
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ObiHai ObiPhone 1032 and ObiPhone 1062. It has been classified as critical. The affected element is an unknown function of the component Header Handler. Performing a manipulation results in null termination. Additionally, an exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in ObiHai ObiPhone 1032 and ObiPhone 1062. This affects an unknown code block of the component Header Handler. The manipulation with an unknown input leads to a null termination vulnerability. CWE is classifying the issue as CWE-170. The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 08/18/2016 by David Tomaschik with Google Security Team as ObiHai ObiPhone - Multiple Vulnerabilities as confirmed mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The public release was coordinated with ObiHai. The mailinglist post contains:
Multiple vulnerabilities were discovered in the web management interface of the ObiHai ObiPhone products. The Vulnerabilities were discovered during a black box security assessment and therefore the vulnerability list should not be considered exhaustive.The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
A public exploit has been developed by David Tomaschik in HTTP GET Request and been published immediately after the advisory. The exploit is shared for download at seclists.org. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 98 days. During that time the estimated underground price was around $0-$5k. The code used by the exploit is:
GET / HTTP/1.1 Host: foo Authorization: foo
Upgrading to version 5.0.0 Build 3497 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-90915, VDB-90916, VDB-90917 and VDB-90918. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Null terminationCWE: CWE-170 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: David Tomaschik
Programming Language: 🔍
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Upgrade: ObiPhone 1032/ObiPhone 1062 5.0.0 Build 3497
Timeline
05/12/2016 🔍05/12/2016 🔍
08/18/2016 🔍
08/18/2016 🔍
08/23/2016 🔍
04/01/2019 🔍
Sources
Advisory: ObiHai ObiPhone - Multiple VulnerabilitiesResearcher: David Tomaschik
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-90921
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 08/23/2016 16:58Updated: 04/01/2019 20:57
Changes: 08/23/2016 16:58 (55), 04/01/2019 20:57 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.