Matera Banco 1.0.0 Backend Trace 7pk error

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

Summaryinfo

A vulnerability was found in Matera Banco 1.0.0. It has been declared as problematic. This impacts an unknown function of the component Backend. The manipulation results in 7pk error (Trace). This vulnerability is cataloged as CVE-2018-14925. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Matera Banco 1.0.0. It has been classified as problematic. Affected is some unknown processing of the component Backend. The manipulation with an unknown input leads to a 7pk error vulnerability (Trace). CWE is classifying the issue as CWE-388. This is going to have an impact on confidentiality. CVE summarizes:

Matera Banco 1.0.0 mishandles Java errors in the backend, as demonstrated by a stack trace revealing use of net.sf.acegisecurity components.

The bug was discovered 08/02/2018. The weakness was shared 08/03/2018 (Website). The advisory is shared for download at medium.com. This vulnerability is traded as CVE-2018-14925 since 08/03/2018. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.

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

The entries VDB-122607, VDB-122603, VDB-122605 and VDB-122606 are related to this item. Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.6

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

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Name: Trace
Class: 7pk error / Trace
CWE: CWE-388
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/02/2018 🔍
08/03/2018 +0 days 🔍
08/03/2018 +0 days 🔍
08/03/2018 +0 days 🔍
08/04/2018 +1 days 🔍
04/29/2023 +1729 days 🔍

Sourcesinfo

Advisory: medium.com
Status: Not defined

CVE: CVE-2018-14925 (🔍)
GCVE (CVE): GCVE-0-2018-14925
GCVE (VulDB): GCVE-100-122604
X-Force: 147964

See also: 🔍

Entryinfo

Created: 08/04/2018 08:32
Updated: 04/29/2023 15:00
Changes: 08/04/2018 08:32 (58), 03/13/2020 11:11 (1), 04/29/2023 15:00 (3)
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.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!