LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32775: Any user can see any fields (including mailbox password) with GroupBy Dashlet

Combodo iTop is a web based IT Service Management tool. In versions prior to 2.7.4, a non admin user can get access to many class/field values through GroupBy Dashlet error message. This issue is fixed in versions 2.7.4 and 3.0.0.

HighCVSS 7.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

An authenticated non-admin iTop user could make error messages reveal sensitive internal fields, including mailbox passwords. The business risk is credential and data exposure inside an IT service management platform, not system takeover. Combodo fixed the issue in iTop 2.7.4 and 3.0.0.

Executive priority

Prioritize remediation for any production iTop instance below 2.7.4. The main concern is sensitive data and credential disclosure to ordinary authenticated users, which can create follow-on operational and access risk.

Technical view

CVE-2021-32775 affects Combodo iTop versions before 2.7.4. Through the GroupBy Dashlet error message, a low-privileged user could access many class and field values. CVSS 3.1 is 7.7: network-accessible, low complexity, low privileges required, no user interaction, high confidentiality impact.

Likely exposure

Exposure is limited to organizations running Combodo iTop before 2.7.4, especially where non-admin users can authenticate. Risk is higher when iTop stores sensitive operational fields or mailbox credentials.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. The vulnerability is still concerning because exploitation requires only authenticated low-privileged access and targets confidential data exposed through application errors.

Researcher notes

Evidence identifies CWE-209, indicating sensitive information exposure through error messages. The public bundle names the GroupBy Dashlet path and affected/fixed versions, but does not provide detailed exploit traces, observed exploitation, or separate compensating controls.

Mitigation direction

  • Upgrade Combodo iTop to 2.7.4, 3.0.0, or a later fixed release.
  • Review the Combodo advisory for version-specific upgrade guidance.
  • Restrict iTop access to trusted authenticated users until remediation is complete.
  • Rotate mailbox credentials if a vulnerable deployment was accessible to non-admin users.

Validation and detection

  • Inventory all iTop deployments and record their exact versions.
  • Confirm each deployment is 2.7.4, 3.0.0, or later.
  • Review whether non-admin accounts existed during vulnerable exposure windows.
  • Check whether mailbox passwords or sensitive class fields were stored in iTop.
Prepared
Confidence
high
Sources
3

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-209: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-2021-32775 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.7 (3.1)
Known Exploited
No
Published

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

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
2Source 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.7CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N3.14Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.7High
CVSS 3.1 vector shape for CVE-2021-32775Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
CombodoiTop< 2.7.4Listed
Weakness

CWE details

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

CWE-209 · source CWE mapping

Generation of Error Message Containing Sensitive Information

Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.