Rico só vantagem pra investir App up to 4.58.32.12421 on Android br.com.rico.mobile SegmentSettingsModule.java SEGMENT_WRITE_KEY hard-coded key

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.
3.0$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Rico só vantagem pra investir App up to 4.58.32.12421 on Android. Impacted is an unknown function of the file br/com/rico/mobile/di/SegmentSettingsModule.java of the component br.com.rico.mobile. Performing a manipulation of the argument SEGMENT_WRITE_KEY results in hard-coded key. This vulnerability is identified as CVE-2026-5453. The attack is only possible with local access. Additionally, an exploit exists. The vendor was contacted early about this disclosure but did not respond in any way.

Detailsinfo

A vulnerability classified as problematic has been found in Rico só vantagem pra investir App up to 4.58.32.12421 on Android. This affects an unknown functionality of the file br/com/rico/mobile/di/SegmentSettingsModule.java of the component br.com.rico.mobile. The manipulation of the argument SEGMENT_WRITE_KEY with an unknown input leads to a hard-coded key vulnerability. CWE is classifying the issue as CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. This is going to have an impact on confidentiality.

The advisory is shared at notion.so. This vulnerability is uniquely identified as CVE-2026-5453. The exploitability is told to be easy. An attack has to be approached locally. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

The exploit is shared for download at notion.so. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-18597). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Hard-coded key
CWE: CWE-321 / CWE-320
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒

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

04/02/2026 VulDB entry created
04/03/2026 +0 days Advisory disclosed
04/03/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: notion.so
Status: Not defined

CVE: CVE-2026-5453 (🔒)
GCVE (CVE): GCVE-0-2026-5453
GCVE (VulDB): GCVE-100-355041
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20130704

Entryinfo

Created: 04/03/2026 00:16
Updated: 04/03/2026 12:18
Changes: 04/03/2026 00:16 (59), 04/03/2026 12:18 (1)
Complete: 🔍
Submitter: fxizenta
Cache ID: 216::103

Submitinfo

Accepted

  • Submit #781758: RICO.COM.VC Rico(br.com.rico.mobile) 4.58.32.12421 Segment Write Key Exposure (by fxizenta)

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!