dbcve.org
Single ConnectApplication · Krontech

CVE-2021-44792

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-27
Fix available
A fix is available. Upgrade to 2.16 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Single Connect does not perform an authorization check when using the "log-monitor" module. A remote attacker could exploit this vulnerability to access the logging interface. The exploitation of this vulnerability might allow a remote attacker to obtain sensitive information.

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 · moderate confidence

Single Connect's 'log-monitor' module lacks proper authorization checks, allowing unauthenticated remote attackers to access the logging interface. This enables attackers to potentially view sensitive system information, logs, or debugging data without any credentials.

MitigationImplement robust authorization checks on the log-monitor module to ensure only authenticated and authorized users can access logging functionality. Additionally, restrict network access to the logging interface to trusted IP addresses or networks.

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
Single ConnectApplication
Affected:< 2.16

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 the installed Single Connect product
    Locate the Krontech Single Connect installation and determine the installed version number. This may be found in the product's about page, system information, or version file.
    Affected if The installed version is Krontech Single Connect and the version is below 2.16 (e.g., 2.15, 2.14, etc.)
  2. Determine if the log-monitor module is enabled
    Check the Single Connect configuration settings or module list to see if the 'log-monitor' module is currently enabled or active on the system.
    Affected if The log-monitor module is enabled and active on the system
  3. Verify network accessibility of the logging interface
    Attempt to access the logging interface endpoint (typically via HTTP/HTTPS to the log-monitor path) from an unauthenticated context, or review firewall/network rules that control access to the logging port/interface.
    Affected if The logging interface is reachable over the network without requiring authentication credentials
  4. Check for existing authorization controls on log-monitor
    Review the security or access control settings for the log-monitor module within Single Connect to determine if any authentication or authorization requirements are configured.
    Affected if No authentication or authorization is required to access the log-monitor interface, or the module explicitly allows unauthenticated access

A system is affected if it runs Krontech Single Connect version below 2.16 with the log-monitor module enabled and accessible without authentication credentials.

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 2.16 or later
Fixed in 2.16
Interim mitigation

Implement robust authorization checks on the log-monitor module to ensure only authenticated and authorized users can access logging functionality. Additionally, restrict network access to the logging interface to trusted IP addresses or networks.

Recommended fix High confidence

2.16

  1. 1. Backup the current Single Connect configuration and database
  2. 2. Download Single Connect version 2.16 from the official vendor repository
  3. 3. Stop the Single Connect service
  4. 4. Install or apply the version 2.16 update
  5. 5. Verify the installation was successful
  6. 6. Start the Single Connect service
  7. 7. Confirm the log-monitor module now performs authorization checks

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

Fix this in Single Connect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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