LiveActive security incident?Get immediate response
CVE Record

CVE-2020-5943: In versions 14.1.0-14.1.0.1 and 14.1.2.5-14.1.2.7, when a BIG-IP object is created or listed through the RE...

In versions 14.1.0-14.1.0.1 and 14.1.2.5-14.1.2.7, when a BIG-IP object is created or listed through the REST interface, the protected fields are obfuscated in the REST response, not protected via a SecureVault cryptogram as TMSH does. One example of protected fields is the GTM monitor password.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Certain F5 BIG-IP 14.1 releases returned protected values from the REST interface in a weaker form than TMSH uses. A password-like field, such as a GTM monitor password, could appear obfuscated in REST output rather than protected with a SecureVault cryptogram. This raises secret-exposure risk where REST access is available.

Executive priority

Prioritize inventory and vendor-guidance review, especially for internet-adjacent or broadly reachable management planes. Business risk is credential leakage from network infrastructure, but public severity and exploitation evidence are incomplete in the provided sources.

Technical view

CVE-2020-5943 affects BIG-IP versions 14.1.0-14.1.0.1 and 14.1.2.5-14.1.2.7. When objects are created or listed through REST, protected fields are obfuscated in REST responses instead of protected via SecureVault cryptograms as in TMSH. Public source data provides no CVSS, CWE, or detailed exploit prerequisites.

Likely exposure

Exposure appears limited to organizations running the listed BIG-IP 14.1 versions and using or allowing REST interface access. The sources do not state whether authentication is required, whether management exposure is needed, or which object types beyond the example GTM monitor password are affected.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV in the supplied bundle. Treat this as a potential credential-disclosure issue until vendor guidance, version inventory, and access controls are confirmed.

Researcher notes

The key technical distinction is obfuscation versus SecureVault cryptogram protection in REST responses. The source bundle names GTM monitor password as one example protected field but does not enumerate all affected fields, required privileges, attack complexity, or remediation details.

Mitigation direction

  • Review F5 advisory K20059815 for fixed versions or vendor-recommended actions.
  • Inventory BIG-IP systems for versions 14.1.0-14.1.0.1 and 14.1.2.5-14.1.2.7.
  • Restrict REST interface access to trusted administration paths only.
  • Rotate exposed monitor or object credentials if REST responses may have been captured.
  • Preserve logs before making changes if exposure is suspected.

Validation and detection

  • Confirm each BIG-IP version against the affected version ranges.
  • Identify systems where BIG-IP REST access is enabled or reachable.
  • Review administrative logs for REST object create or list activity.
  • Check whether protected fields were returned in stored responses, logs, or tooling.
  • Document whether vendor guidance requires upgrade, workaround, or credential rotation.
Prepared
Confidence
medium
Sources
3

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-5943 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aBIG-IP14.1.0-14.1.0.1, 14.1.2.5-14.1.2.7Listed
Weakness

CWE details

No CWE listed

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