dbcve.org
On PremiseApplication · Itarian

CVE-2022-25151

HIGH · 7.5 CVSS v3.1 Published 2022-06-09
Fix available
A fix is available. Upgrade to 6.35.37347.20040 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Within the Service Desk module of the ITarian platform (SAAS and on-premise), a remote attacker can obtain sensitive information, caused by the failure to set the HTTP Only flag. A remote attacker could exploit this vulnerability to gain access to the management interface by using this vulnerability in combination with a successful Cross-Site Scripting attack on a user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Service Desk module in ITarian (both SAAS and on-premise) fails to set the HTTP Only flag on session cookies. This allows JavaScript code injected via XSS to access and exfiltrate session cookies, enabling attackers to hijack authenticated user sessions and gain access to the management interface.

MitigationConfigure the Service Desk module to set the HTTP Only flag on all session cookies. Until the vendor patch is applied, users should be protected from XSS attacks through input validation and Content Security Policy.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
On PremiseApplication
Affected:< 6.35.37347.20040
Saas Service DeskApplication
Affected:< 6.35.37347.20040

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Itarian product variant
    Determine whether you are running Itarian On Premise or Itarian SaaS Service Desk. Check the product documentation, about page, or login screen for the product name.
    Affected if Running either Itarian On Premise or SaaS Service Desk
  2. Check the installed version number
    Locate the version information in the Itarian application (typically in Help > About or System > Version). Compare the version to 6.35.37347.20040.
    Affected if Version is lower than 6.35.37347.20040
  3. Verify Service Desk module is enabled
    Check if the Service Desk module is active in your Itarian installation. This is usually found in the modules or plugins section of the administration console.
    Affected if Service Desk module is enabled and in use
  4. Inspect session cookies for HTTP Only flag
    Log into the Service Desk interface, open browser developer tools (F12), go to Application > Cookies, and examine each session cookie. Alternatively, capture a login response with curl or a proxy and check the Set-Cookie headers for the presence of the HttpOnly attribute.
    Affected if Session cookies do NOT contain the HttpOnly attribute in their Set-Cookie header or cookie definition

You are affected if your Itarian version is below 6.35.37347.20040, the Service Desk module is enabled, and your session cookies lack the HttpOnly flag.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.35.37347.20040 or later
Fixed in 6.35.37347.20040
Interim mitigation

Configure the Service Desk module to set the HTTP Only flag on all session cookies. Until the vendor patch is applied, users should be protected from XSS attacks through input validation and Content Security Policy.

Recommended fix High confidence

6.35.37347.20040 or later

  1. Upgrade the ITarian Service Desk (both On-Premise and SaaS) to version 6.35.37347.20040 or later
  2. After upgrade, verify that the HTTP Only flag is set on session cookies by inspecting Set-Cookie headers in browser developer tools or using a web vulnerability scanner
  3. Test that the application functions normally after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in On Premise Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25151 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data