LiveActive security incident?Get immediate response
CVE Record

CVE-2022-31058: SQL injection via the field name of a tracker in Tuleap

Tuleap is a Free & Open Source Suite to improve management of software developments and collaboration. In versions prior to 13.9.99.95 Tuleap does not sanitize properly user inputs when constructing the SQL query to retrieve data for the tracker reports. An attacker with the capability to create a new tracker can execute arbitrary SQL queries. Users are advised to upgrade. There is no known workaround for this issue.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-31058 is a high-severity SQL injection in Tuleap before 13.9.99.95. A user who can create a tracker may cause arbitrary SQL execution through tracker report handling. The main business concern is database compromise affecting confidentiality, integrity, and availability.

Executive priority

Prioritize remediation for any affected Tuleap instance, especially production systems containing sensitive project or collaboration data. The privilege requirement lowers broad internet-risk, but database impact is high.

Technical view

Tuleap improperly sanitized user-controlled tracker field names while building SQL queries for tracker report data retrieval. The issue is classified as CWE-89 with CVSS 3.1 score 7.2. Exploitation requires network access and high privileges, specifically the capability to create a new tracker.

Likely exposure

Exposure is limited to Enalean Tuleap deployments running versions earlier than 13.9.99.95. Risk is higher where tracker creation is delegated beyond tightly trusted administrators.

Exploitation context

The bundle does not identify active exploitation, and KEV is false. The vulnerability is still serious because successful exploitation can execute arbitrary SQL, but the cited conditions require elevated application capability.

Researcher notes

Focus validation on version exposure and tracker creation capability. The public description supports SQL injection through tracker field names in report retrieval, but does not provide exploit telemetry or a workaround.

Mitigation direction

  • Upgrade Tuleap to version 13.9.99.95 or later.
  • Review vendor advisory and commit notes before remediation.
  • Do not rely on a workaround; the advisory states none is known.
  • Restrict tracker creation to trusted administrators until upgraded.

Validation and detection

  • Inventory Tuleap deployments and record exact versions.
  • Confirm no instance remains below 13.9.99.95.
  • Review tracker creation permissions for excessive delegation.
  • Check change records for successful Tuleap upgrade completion.
Prepared
Confidence
high
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 · 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-2022-31058 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

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

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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-31058Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
Enaleantuleap< 13.9.99.95Listed
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.