LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10014: arekk uke finder.rb sql injection

A vulnerability classified as critical has been found in arekk uke. This affects an unknown part of the file lib/uke/finder.rb. The manipulation leads to sql injection. The identifier of the patch is 52fd3b2d0bc16227ef57b7b98a3658bb67c1833f. It is recommended to apply a patch to fix this issue. The identifier VDB-217485 was assigned to this vulnerability.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2015-10014 is a SQL injection issue in arekk uke, specifically tied to lib/uke/finder.rb. A low-privileged attacker on an adjacent attack path could affect confidentiality, integrity, and availability at a limited level. The public record names a patch commit, but affected versions are not specified.

Executive priority

Treat as a moderate-priority cleanup unless uke is deployed in sensitive workflows. The risk is real because SQL injection can affect data, but public evidence here does not show internet-scale exposure or active exploitation.

Technical view

The vulnerability is classified as CWE-89 SQL injection in arekk/uke. CVSS v3.1 is 5.5 with AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. The source bundle identifies patch commit 52fd3b2d0bc16227ef57b7b98a3658bb67c1833f. Version scope is listed as n/a.

Likely exposure

Exposure is likely limited to systems that include the arekk uke project or code derived from it. Because affected versions and CPEs are not provided, teams need source or dependency inventory rather than product-version matching alone.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires adjacent access and low privileges, with no user interaction. No exploit steps are provided in the source bundle.

Researcher notes

Key uncertainty is version scope: the record lists affected versions as n/a. Validation should focus on code presence and patch comparison. Avoid assuming downstream packages, forks, or deployment models are affected without confirming the vulnerable finder.rb code path exists.

Mitigation direction

  • Apply the referenced upstream patch commit where arekk uke is used.
  • Check vendor or project guidance for any maintained release containing the fix.
  • Reduce database permissions used by affected application code.
  • Restrict access to systems embedding uke where operationally possible.
  • Prioritize remediation if uke handles sensitive or business-critical data.

Validation and detection

  • Inventory repositories and dependencies for arekk uke usage.
  • Compare lib/uke/finder.rb against the referenced patched commit.
  • Confirm deployed artifacts contain the patched finder.rb logic.
  • Run existing unit and integration tests around database lookup behavior.
  • Review application logs for unusual database errors or suspicious lookup patterns.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2015-10014 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2015-10014Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
arekkuken/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.