LiveActive security incident?Get immediate response
CVE Record

CVE-2020-27523: Solstice-Pod up to 5.0.2 WEBRTC server mishandles the format-string specifiers %x; %p; %c and %s in the scr...

Solstice-Pod up to 5.0.2 WEBRTC server mishandles the format-string specifiers %x; %p; %c and %s in the screen_key, display_name, browser_name, and operation_system parameter during the authentication process. This may crash the server and force Solstice-Pod to reboot, which leads to a denial of service.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-27523 can let an unauthenticated party crash a Solstice-Pod WebRTC server during authentication, forcing the device to reboot. The main business impact is meeting-room or classroom display outage, not proven data theft. Public scoring is incomplete in the provided record.

Executive priority

Prioritize remediation where pods support executive rooms, classrooms, incident rooms, or customer-facing collaboration spaces. The vulnerability is operationally disruptive and public, but available evidence does not show data compromise or confirmed active exploitation.

Technical view

Solstice-Pod versions up to 5.0.2 mishandle format-string specifiers in authentication parameters including screen_key, display_name, browser_name, and operation_system. The CVE states this can crash the WebRTC server and reboot the pod, causing denial of service.

Likely exposure

Exposure is most likely where Solstice-Pod devices are deployed in conference rooms, classrooms, or shared presentation spaces and their WebRTC/authentication service is reachable from user, guest, or adjacent networks.

Exploitation context

The source bundle cites public discussion and a blog/video reference, but CISA KEV is false and no cited source in the bundle establishes confirmed active exploitation. Treat this as publicly known denial-of-service risk, not confirmed in-the-wild exploitation.

Researcher notes

The CVE record lacks CVSS, CWE, and structured affected CPE data. Analysis should stay anchored to the description: unauthenticated authentication-parameter format-string handling causes crash and reboot. Validate exposure through inventory and reachability, not exploit reproduction.

Mitigation direction

  • Inventory Solstice-Pod devices and identify any running version 5.0.2 or earlier.
  • Check current Mersive guidance for fixed firmware or supported remediation.
  • Restrict pod access to trusted presentation networks only.
  • Reduce guest or unmanaged network reachability to the WebRTC service.
  • Monitor room-device reboot patterns until remediation is complete.

Validation and detection

  • Confirm whether Solstice-Pod assets exist in meeting or classroom networks.
  • Record firmware versions and flag devices at 5.0.2 or earlier.
  • Review network paths to the pod authentication service.
  • Check device uptime, reboot history, and support logs for unexplained crashes.
  • Document vendor remediation status for each affected device.
Prepared
Confidence
medium
Sources
6

Public sources used

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-27523 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
5Source 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/an/an/aListed
Weakness

CWE details

No CWE listed

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