dbcve.org
AtviseApplication

CVE-2022-21184

MEDIUM · 5.9 CVSS v3.1 Published 2022-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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
An information disclosure vulnerability exists in the License registration functionality of Bachmann Visutec GmbH Atvise 3.5.4, 3.6 and 3.7. A plaintext HTTP request can lead to a disclosure of login credentials. An attacker can perform a man-in-the-middle attack to trigger this vulnerability.

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

The License registration functionality in Bachmann Visutec Atvise versions 3.5.4, 3.6, and 3.7 transmits login credentials in plaintext HTTP. An attacker positioned on the network path (MITM) can intercept these credentials as they travel unencrypted between client and server.

MitigationEnable HTTPS/TLS encryption for all License registration traffic and ensure the application enforces secure connections. Additionally, upgrade to a patched version if available from the vendor.

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
AtviseApplication
Affected:= 3.5.4= 3.6= 3.7

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/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 the installed Atvise version
    Check the application version by accessing the Atvise about page, checking the installation directory for version files, or querying the application directly through its web interface or configuration panel. Common locations include the installation folder or the application's built-in version info.
    Affected if The installed version matches exactly 3.5.4, 3.6, or 3.7.
  2. Locate the License registration endpoint
    Examine the Atvise server configuration files (such as configuration.xml, server.config, or similar) to identify the URL or endpoint used for license registration. Look for paths related to licensing or registration functionality.
    Affected if The license registration endpoint uses an HTTP (not HTTPS) URL.
  3. Verify the server is listening on HTTP port
    Check which network ports the Atvise server is listening on. Use netstat, ss, or the server configuration to confirm that the application accepts connections on port 80 (HTTP). Also verify whether port 443 (HTTPS) is configured and active.
    Affected if The server accepts plaintext HTTP connections on port 80 for the license registration functionality.
  4. Inspect the web server configuration for TLS settings
    Review the Atvise web server configuration (such as nginx.conf, Apache config, or Atvise's internal server settings) to determine if TLS/SSL is enabled and enforced for the license registration route. Check for SSL/TLS certificate configuration.
    Affected if TLS is not enabled or is optional for the license registration traffic, allowing plaintext transmission.
  5. Capture network traffic to confirm plaintext transmission
    Use a network packet capture tool (such as Wireshark or tcpdump) on the client or network segment to observe the actual traffic when performing a license registration. Inspect the captured packets for plaintext credentials.
    Affected if Login credentials are transmitted in cleartext over HTTP during the license registration process.

You are affected if the installed Atvise version is exactly 3.5.4, 3.6, or 3.7 AND the license registration functionality uses plaintext HTTP instead of HTTPS, allowing credentials to be intercepted by a network attacker.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable HTTPS/TLS encryption for all License registration traffic and ensure the application enforces secure connections. Additionally, upgrade to a patched version if available from the vendor.

Fix this in Atvise Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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