CVE-2020-28856: OpenAsset Digital Asset Management (DAM) through 12.0.19 does not correctly determine the HTTP request's or...
OpenAsset Digital Asset Management (DAM) through 12.0.19 does not correctly determine the HTTP request's originating IP address, allowing attackers to spoof it using X-Forwarded-For in the header, by supplying localhost address such as 127.0.0.1, effectively bypassing all IP address based access controls.
Security readout for executives and security teams
OpenAsset DAM could be tricked into believing a request came from a trusted internal address. If an organization used IP allowlists inside OpenAsset as a security boundary, an outside attacker may bypass those checks. The sources do not provide CVSS scoring or confirm active exploitation. Exposure is most likely where OpenAsset DAM is reachable by untrusted networks and uses application-level IP restrictions to protect administrative, internal, or restricted content paths. Treat this as a targeted access-control risk, not a broad emergency. Prioritize environments where OpenAsset is internet-facing or protects sensitive assets using IP restrictions. Mitigation focus: Check OpenAsset vendor guidance for fixed versions or supported workarounds.; Upgrade beyond affected OpenAsset versions if vendor guidance identifies a fix.; Do not rely solely on OpenAsset application-level IP access controls..
Prepared
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.
cve · low confidence lookup
CVE-2020-28856 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
3Timeline events
1ADP providers
2Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 14, 2020, 17:59 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.