ReadA up to 1.1.0.2 SQL sql injection

Summaryinfo

A vulnerability classified as critical has been found in ReadA up to 1.1.0.2. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in sql injection (SQL). This vulnerability was named CVE-2018-10595. The attack needs to be approached within the local network. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, was found in ReadA up to 1.1.0.2. This affects some unknown processing. The manipulation with an unknown input leads to a sql injection vulnerability (SQL). CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A vulnerability in ReadA version 1.1.0.2 and previous allows an authorized user with access to a privileged account on a BD Kiestra system (Kiestra TLA, Kiestra WCA, and InoqulA+ specimen processor) to issue SQL commands, which may result in loss or corruption of data.

The bug was discovered 05/22/2018. The weakness was presented 05/24/2018 (Website). The advisory is shared at bd.com. This vulnerability is uniquely identified as CVE-2018-10595 since 05/01/2018. Access to the local network is required for this attack to succeed. Required for exploitation is a authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 2 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.

See VDB-118172 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• ReadA

Version

• 1.1.0.0
• 1.1.0.1
• 1.1.0.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion