LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44792: Information Leakege via Unauthorized Access in Single Connect

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Kron Single Connect has an authorization flaw in its log-monitor module. An unauthenticated remote attacker may reach the logging interface and view sensitive information. The business risk is data exposure, not system takeover, based on the provided CVSS and description.

Executive priority

Treat this as a moderate-priority exposure review. Prioritize internet-facing or third-party-accessible Single Connect systems because unauthenticated log access may disclose sensitive operational data.

Technical view

CVE-2021-44792 is a CWE-862 missing authorization check in Kron Single Connect's log-monitor module. The CVSS 3.1 vector is network-exploitable, low complexity, no privileges, no user interaction, with low confidentiality impact and no integrity or availability impact.

Likely exposure

Exposure is likely limited to organizations running Kron Single Connect with the log-monitor interface reachable from untrusted networks. Affected versions are unspecified in the provided source bundle.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability is remotely reachable and unauthenticated, but only information disclosure is described.

Researcher notes

The record names Kron Single Connect and the log-monitor module, but affected versions and patch details are not provided. Avoid assuming exploitability beyond unauthorized logging-interface access and potential sensitive information disclosure.

Mitigation direction

  • Identify all Kron Single Connect deployments and exposed management or logging interfaces.
  • Check Kron and cited government guidance for affected versions and fixes.
  • Restrict log-monitor and administrative interfaces to trusted networks only.
  • Disable or block unused logging interfaces after vendor validation.
  • Monitor for unusual access to Single Connect logging endpoints.

Validation and detection

  • Confirm whether Kron Single Connect is deployed in the environment.
  • Verify product version and configuration against vendor or government advisories.
  • Confirm log-monitor is not reachable anonymously from untrusted networks.
  • Review access logs for unexpected log-monitor interface activity.
  • Document compensating controls where version status remains uncertain.
Prepared
Confidence
medium
Sources
4

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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
cve · low confidence lookup

CVE-2021-44792 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
3Timeline events
1ADP providers
3Source 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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-44792Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
KronSingle Connectunspecifiedunaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.