CVE Intelligence
Skip to main content
MEDIUM

CVE-2024-45838

CVE-2024-45838 — goTenna Pro ATAK Plugin Cleartext Transmission of Sensitive Information

The goTenna Pro ATAK Plugin does not encrypt callsigns in messages. It is advised to not use sensitive information in callsigns when using this and previous versions of the plugin. Update to current plugin version which uses AES-256 encryption for callsigns in encrypted operation

Published Updated Sources: cvelistV5, icscert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

gotenna

pro_atak_plugin

CVSS base

4.3

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

gotenna

Products (1)

pro atak plugin

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
4.3CVSS 3.1MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-319

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1056.004Input Capture: Credential API Hooking
  • T1040Network Sniffing

References

1 on the record

Elsewhere on this site

  • gotennaevery CVE for this vendor
  • CWE-319other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.