dbcve.org
Single ConnectApplication · Krontech

CVE-2021-44793

HIGH · 8.6 CVSS v3.1 Published 2022-01-27
Fix available
A fix is available. Upgrade to 2.16 or later.
See remediation →
95/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
Single Connect does not perform an authorization check when using the sc-reports-ui" module. A remote attacker could exploit this vulnerability to access the device configuration page and export the data to an external file. The exploitation of this vulnerability might allow a remote attacker to obtain sensitive information including the database credentials. Since the database runs with high privileges it is possible to execute commands with the attained credentials.

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

CVE-2021-44793 is an authorization bypass vulnerability in the sc-reports-ui module of Single Connect. A remote attacker can access the device configuration page and export data without authentication, potentially exposing database credentials. Since the database runs with high privileges, attackers can execute commands with the attained credentials.

MitigationApply vendor patches for Single Connect immediately. If no patch is available, implement compensating controls such as network segmentation, firewall rules restricting access to the sc-reports-ui interface, and multi-factor authentication for administrative interfaces.

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

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

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 Single Connect installation
    Locate the Single Connect application on the system or check the product version via the system's package manager, software inventory, or administrative interface
    Affected if Single Connect is installed and the version is unknown or less than 2.16
  2. Determine Single Connect version
    Access the administrative console, check the software manifest, or use the vendor-provided version query mechanism to obtain the exact installed version number
    Affected if The installed version is lower than 2.16 (e.g., 2.15.x, 2.14.x, etc.)
  3. Verify sc-reports-ui module exposure
    Check the web server configuration or application modules list to confirm whether the sc-reports-ui component is loaded and accessible
    Affected if The sc-reports-ui module is present and enabled on the system
  4. Test unauthenticated access to configuration pages
    Attempt to access the device configuration page or data export endpoints via HTTP/HTTPS requests without providing credentials
    Affected if The configuration page or export functions are accessible without authentication (HTTP response returns 200 OK instead of redirecting to login)
  5. Check network accessibility of sc-reports-ui
    Review firewall rules, network ACLs, or access control lists to determine if the sc-reports-ui interface is exposed to untrusted networks or the internet
    Affected if The sc-reports-ui interface is reachable from untrusted networks or the internet without restriction

A system is affected if it runs Krontech Single Connect with version lower than 2.16 and has the sc-reports-ui module exposed to network access where unauthenticated configuration or data export is possible.

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

Apply vendor patches for Single Connect immediately. If no patch is available, implement compensating controls such as network segmentation, firewall rules restricting access to the sc-reports-ui interface, and multi-factor authentication for administrative interfaces.

Recommended fix High confidence

2.16

  1. Backup the current Single Connect configuration and database before initiating the upgrade
  2. Obtain Single Connect version 2.16 or later from the official vendor distribution channel
  3. Apply the upgrade to the Single Connect instance following the standard upgrade procedure
  4. After upgrade, verify that the sc-reports-ui module now performs proper authorization checks
  5. Confirm the configuration page is no longer accessible without authentication

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
  • 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-2021-44793 — 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-44793 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