LiveActive security incident?Get immediate response
CVE Record

CVE-2015-10027: hydrian TTRSS-Auth-LDAP Username ldap injection

A vulnerability, which was classified as problematic, has been found in hydrian TTRSS-Auth-LDAP. Affected by this issue is some unknown functionality of the component Username Handler. The manipulation leads to ldap injection. Upgrading to version 2.0b1 is able to address this issue. The patch is identified as a7f7a5a82d9202a5c40d606a5c519ba61b224eb8. It is recommended to upgrade the affected component. VDB-217622 is the identifier 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-10027 affects hydrian TTRSS-Auth-LDAP, an LDAP authentication plugin. A username handling flaw can allow LDAP injection, potentially affecting confidentiality, integrity, and availability at a limited level. The documented fix is upgrading to version 2.0b1 or applying the referenced patch.

Executive priority

Treat this as a moderate-priority authentication component issue. It is not documented as actively exploited, but affected systems should be upgraded because authentication flaws can become higher-impact when combined with weak network boundaries or reused credentials.

Technical view

The vulnerability is CWE-90 LDAP injection in the Username Handler of hydrian TTRSS-Auth-LDAP. The CVSS 3.1 score is 5.5 with adjacent-network attack vector, low complexity, low privileges required, no user interaction, and low impact across confidentiality, integrity, and availability.

Likely exposure

Exposure is likely limited to environments running hydrian TTRSS-Auth-LDAP, especially older versions before 2.0b1. The source bundle does not identify exact vulnerable version ranges beyond recommending the 2.0b1 upgrade.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. CVSS indicates exploitation requires adjacent network access and low privileges, which reduces broad internet-scale urgency but still matters for shared networks and authenticated environments.

Researcher notes

Evidence is thin on affected version boundaries and vulnerable function details. The strongest source-grounded facts are CWE-90, Username Handler involvement, CVSS 5.5, and remediation via release 2.0b1 or commit a7f7a5a82d9202a5c40d606a5c519ba61b224eb8.

Mitigation direction

  • Upgrade hydrian TTRSS-Auth-LDAP to version 2.0b1.
  • Verify patch a7f7a5a82d9202a5c40d606a5c519ba61b224eb8 is present.
  • Prioritize systems where LDAP authentication is reachable from shared networks.
  • Check GitHub and VulDB for any newer vendor guidance.
  • Retire or isolate unmaintained plugin deployments if upgrade is not possible.

Validation and detection

  • Inventory TT-RSS deployments using hydrian TTRSS-Auth-LDAP.
  • Confirm installed plugin version is 2.0b1 or later.
  • Review deployed code for the referenced patch commit.
  • Validate LDAP username handling in a controlled test environment.
  • Check logs for unusual authentication failures or LDAP query errors.
Prepared
Confidence
medium
Sources
7

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

CVE-2015-10027 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
6Source 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-10027Attack 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
hydrianTTRSS-Auth-LDAPn/aListed
Weakness

CWE details

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

CWE-90 · source CWE mapping

Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')

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