dbcve.org
Kalay P2p Software Development KitApplication · Throughtek

CVE-2021-32934

HIGH · 7.5 CVSS v3.1 Published 2022-05-19
Fix available
A fix is available. Upgrade to after 3.1.5 or later.
See remediation →
84/100
Remediation priority · High
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
The affected ThroughTek P2P products (SDKs using versions before 3.1.5, any versions with nossl tag, device firmware not using AuthKey for IOTC conneciton, firmware using AVAPI module without enabling DTLS mechanism, and firmware using P2PTunnel or RDT module) do not sufficiently protect data transferred between the local device and ThroughTek servers. This can allow an attacker to access sensitive information, such as camera feeds.

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

ThroughTek P2P SDK products before version 3.1.5, or configurations using nossl tags, missing AuthKey for IOTC connections, or AVAPI without DTLS, fail to encrypt data in transit between IoT camera devices and ThroughTek servers. This allows unauthenticated attackers on the network path to intercept sensitive streams including camera feeds.

MitigationUpdate ThroughTek P2P SDK to version 3.1.5 or later, enable SSL/TLS encryption, enable DTLS for AVAPI modules, and implement AuthKey authentication for IOTC connections.

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
Kalay P2p Software Development KitApplication
Affected:<= 3.1.5

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

CVSS:3.1/AV:N/AC:L/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 ThroughTek Kalay P2P SDK installation
    Locate the ThroughTek Kalay P2P SDK library files in your IoT camera device firmware or software installation. Check for files named libIOTC.so, libAVAPI.so, or similar ThroughTek SDK components.
    Affected if The SDK library version is 3.1.5 or earlier when queried
  2. Check for nossl configuration tag
    Inspect the SDK configuration files or initialization code for the presence of 'nossl' tags or flags that disable SSL/TLS encryption for P2P connections.
    Affected if nossl tag or no-ssl configuration option is present or enabled
  3. Verify AuthKey configuration for IOTC connections
    Review the IOTC (IoT Over The Cloud) connection configuration to confirm whether an AuthKey is properly set and required for authentication.
    Affected if AuthKey is not configured, missing, or set to empty for IOTC connections
  4. Confirm DTLS status for AVAPI module
    Check the AVAPI module configuration to determine whether DTLS (Datagram Transport Layer Security) encryption is enabled for audio/video streams.
    Affected if DTLS is disabled, not configured, or absent for AVAPI module communications
  5. Verify encryption is enforced on P2P data transport
    Inspect network traffic or SDK logs to confirm whether data between camera devices and ThroughTek servers is encrypted in transit.
    Affected if Network captures show unencrypted video/audio data flowing to ThroughTek servers or P2P traffic lacks TLS/DTLS encryption

Your environment is affected if the ThroughTek Kalay P2P SDK version is 3.1.5 or earlier, or if nossl tags are used, or if AuthKey is missing for IOTC connections, or if DTLS is disabled for AVAPI, resulting in unencrypted camera feed transmission.

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 a release after 3.1.5
Interim mitigation

Update ThroughTek P2P SDK to version 3.1.5 or later, enable SSL/TLS encryption, enable DTLS for AVAPI modules, and implement AuthKey authentication for IOTC connections.

Recommended fix High confidence

Kalay P2p SDK version 3.1.5 or later

  1. Identify all products, devices, or applications using the Kalay P2p Software Development Kit
  2. Determine the current version of the Kalay P2p SDK in use by reviewing project dependencies or firmware versions
  3. Upgrade the Kalay P2p SDK to version 3.1.5 or later from the official ThroughTek distribution channel
  4. If using firmware with AVAPI module, ensure DTLS mechanism is enabled in the configuration
  5. If using P2PTunnel or RDT module, apply the updated SDK and verify secure configuration
  6. Verify the upgrade was successful and confirm the new version is >= 3.1.5
  7. Test the updated system to ensure camera feeds and data are properly protected

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

Fix this in Kalay P2p Software Development Kit Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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