dbcve.org
Manager\+agentsApplication · Signiant

CVE-2022-22795

CRITICAL · 9.1 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 13.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Signiant - Manager+Agents XML External Entity (XXE) - Extract internal files of the affected machine An attacker can read all the system files, the product is running with root on Linux systems and nt/authority on windows systems, which allows him to access and extract any file on the systems, such as passwd, shadow, hosts and so on. By gaining access to these files, attackers can steal sensitive information from the victims machine.

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

Signiant Manager+Agents contains an XML External Entity (XXE) injection vulnerability that allows authenticated attackers to craft malicious XML payloads referencing external entities. Since the application runs with root privileges on Linux or nt/authority on Windows, attackers can read any file accessible to the service account, including system files like /etc/passwd, /etc/shadow, and Windows equivalents.

MitigationDisable XML external entity processing in the XML parser configuration and apply any available vendor patches. Additionally, run the Signiant services with least-privilege user accounts instead of root or SYSTEM to limit the impact of successful exploitation.

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
Manager\+agentsApplication
Affected:< 13.5= 14.0= 15.0

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
High

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

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. Confirm Signiant Manager+Agents installation
    On Linux, run 'rpm -qa | grep -i signiant' or check for /opt/signiant directory. On Windows, check Program Files for Signiant installation or look in Windows Services for Signiant-related services.
    Affected if The product is installed and running.
  2. Identify installed version
    On Linux, run 'rpm -q <package-name>' or check version files in the installation directory. On Windows, check the 'Version' property of the executable in Program Files or use 'wmic product get name,version'. Compare the discovered version to the affected ranges: versions < 13.5, or exactly 14.0, or exactly 15.0.
    Affected if The installed version falls within < 13.5, = 14.0, or = 15.0.
  3. Check service account privileges on Linux
    Run 'ps aux | grep -i signiant' to identify the process user, or check the service init script and /etc/passwd for the signiant service account.
    Affected if The Signiant service runs as root user.
  4. Check service account privileges on Windows
    Open Services console, locate Signiant services, right-click and select Properties, then check the 'Log On' account. Alternatively, run 'sc query' or 'wmic service get name,startname' for Signiant services.
    Affected if The Signiant service runs as 'LocalSystem' or 'NT AUTHORITY\System'.

Your environment is affected if Signiant Manager+Agents is installed with a version less than 13.5, equal to 14.0, or equal to 15.0, AND the service runs with elevated privileges (root on Linux or SYSTEM on Windows), since the XXE vulnerability can then be exploited to read sensitive system files.

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.

From vendor data
Upgrade available Upgrade to 13.5 or later
Fixed in 13.5
Interim mitigation

Disable XML external entity processing in the XML parser configuration and apply any available vendor patches. Additionally, run the Signiant services with least-privilege user accounts instead of root or SYSTEM to limit the impact of successful exploitation.

Fix this in Manager\+agents Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22795 — 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-22795 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