CVE-2021-38461Network attack vector

Protected-data disclosure and forgery via embedded Blowfish key

Published Oct 22, 2021 · Updated Sep 16, 2024

Hard-coded cryptographic key use in AUVESY versiondog 8.0 and earlier allows remote attackers to decrypt or forge data protected by the shared key. The product embeds a Blowfish key in its binaries and reuses it for encryption and decryption, so extracting a binary reveals the secret. No authentication or user interaction is required over the network, but public sources do not identify the protected data or protocol messages governed by the key.

CVSS severity8.2
High
EPSS probability0.55%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded cryptographic key use in AUVESY versiondog 8.0 and earlier allows remote attackers to decrypt or forge data protected by the shared key. The product embeds a Blowfish key in its binaries and reuses it for encryption and decryption, so extracting a binary reveals the secret. No authentication or user interaction is required over the network, but public sources do not identify the protected data or protocol messages governed by the key.

The record

CVE
CVE-2021-38461
Published
Oct 22, 2021
Updated
Sep 16, 2024
Vendor
AUVESY
Product
versiondog
Classifications
CWE-321, T1552.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Oct 22, 2021CVE publishedPublication date reported by the CVE source.
  2. Sep 16, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=All <=8.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

AUVESY · versiondogversion=All <=8.0

Published CVSS scores

8.2CISA ICS-CERTCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
6.4NIST NVDAV:N/AC:L/Au:N/C:P/I:P/A:N
8.2NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-321Use of Hard-coded Cryptographic Key
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo