LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25061: rgb2hex redos

A vulnerability was found in rgb2hex up to 0.1.5. It has been rated as problematic. This issue affects some unknown processing. The manipulation leads to inefficient regular expression complexity. The attack may be initiated remotely. Upgrading to version 0.1.6 is able to address this issue. The patch is named 9e0c38594432edfa64136fdf7bb651835e17c34f. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217151.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-25061 affects rgb2hex, a small color-conversion component. Versions 0.1.0 through 0.1.5 can process certain input inefficiently because of regular expression complexity, potentially reducing availability. The business risk is limited unless the component is deployed in an application path that accepts attacker-controlled input.

Executive priority

Treat this as a routine dependency-remediation item unless rgb2hex is exposed on high-volume public input paths. Prioritize normal patching, not emergency response, based on the sourced low availability-only impact and no confirmed active exploitation.

Technical view

The issue is CWE-1333, inefficient regular expression complexity, in rgb2hex up to 0.1.5. The CVSS 3.1 score is 4.3 with network attack vector, low complexity, low privileges required, no user interaction, and low availability impact only. Version 0.1.6 contains the referenced patch.

Likely exposure

Exposure is likely limited to applications that directly or transitively depend on rgb2hex 0.1.0-0.1.5 and pass remote or low-privileged user input into it. The source bundle does not identify specific downstream products or deployment patterns.

Exploitation context

The sources say the attack may be initiated remotely and requires low privileges. There is no KEV listing and no provided source confirms active exploitation. No exploit status beyond the public vulnerability record should be assumed.

Researcher notes

The public details are sparse: the affected processing is described as unknown, but the weakness is regex complexity. Validate reachability in the local application before assigning operational risk. Do not infer confidentiality or integrity impact from the cited CVSS vector.

Mitigation direction

  • Upgrade rgb2hex to version 0.1.6 or later.
  • Refresh lockfiles and rebuild affected applications after dependency updates.
  • If rgb2hex is transitive, update or replace the parent dependency.
  • Restrict untrusted input reaching color-conversion code where feasible.
  • Check upstream vendor guidance if immediate upgrade is blocked.

Validation and detection

  • Search SBOMs, lockfiles, and dependency manifests for rgb2hex.
  • Confirm no deployed artifact contains versions 0.1.0 through 0.1.5.
  • Identify routes or jobs that process user-supplied color values.
  • Run regression tests after upgrading to 0.1.6 or later.
  • Monitor application performance for unusual request-time spikes.
Prepared
Confidence
medium
Sources
6

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 · low confidence lookup

CWE-1333: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2018-25061 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
5Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2018-25061Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
n/argb2hex0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5Listed
Weakness

CWE details

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

CWE-1333 · source CWE mapping

Inefficient Regular Expression Complexity

Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.