Nextcloud App 2.23.0 on iOS Notification violation of secure design principles

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.6$0-$5k0.00

Summaryinfo

A vulnerability was found in Nextcloud App 2.23.0 on iOS. It has been declared as problematic. This affects an unknown function. The manipulation as part of Notification results in violation of secure design principles. This vulnerability is reported as CVE-2019-15611. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability classified as problematic has been found in Nextcloud App 2.23.0 on iOS (iOS App Software). Affected is some unknown processing. The manipulation as part of a Notification leads to a violation of secure design principles vulnerability. CWE is classifying the issue as CWE-657. The product violates well-established principles for secure design. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Violation of Secure Design Principles in the iOS App 2.23.0 causes the app to leak its login and token to other Nextcloud services when search e.g. for federated users or registering for push notifications.

The weakness was disclosed 02/04/2020. This vulnerability is traded as CVE-2019-15611 since 08/26/2019. It is possible to launch the attack remotely. Additional levels of successful authentication are required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-149656 and VDB-149655 are pretty similar. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.6

VulDB Base Score: 5.9
VulDB Temp Score: 5.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score: 5.9
Vendor Vector: 🔍

NVD Base Score: 4.9
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Violation of secure design principles
CWE: CWE-657
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/26/2019 🔍
02/04/2020 +162 days 🔍
02/05/2020 +1 days 🔍
03/28/2024 +1513 days 🔍

Sourcesinfo

Advisory: hackerone.com
Status: Not defined

CVE: CVE-2019-15611 (🔍)
GCVE (CVE): GCVE-0-2019-15611
GCVE (VulDB): GCVE-100-149652
See also: 🔍

Entryinfo

Created: 02/05/2020 10:46
Updated: 03/28/2024 09:12
Changes: 02/05/2020 10:46 (45), 02/05/2020 10:51 (18), 03/28/2024 09:12 (17)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!