LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25565: In SapphireIMS 5.0, it is possible to use the hardcoded credential in clients (username: sapphire, password...

In SapphireIMS 5.0, it is possible to use the hardcoded credential in clients (username: sapphire, password: ims) and gain access to the portal. Once the access is available, the attacker can inject malicious OS commands on “ping”, “traceroute” and “snmp” functions and execute code on the server.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

SapphireIMS 5.0 reportedly contains a hardcoded client credential that can let an attacker access the portal, then abuse network diagnostic functions to run operating-system commands on the server.

Executive priority

Prioritize this as urgent if SapphireIMS 5.0 is deployed, especially if externally reachable. The business risk is server compromise from a management portal weakness, but evidence for active exploitation is not present here.

Technical view

The issue chains hardcoded portal credentials with OS command injection in the ping, traceroute, and snmp functions. The public CVE text names SapphireIMS 5.0 only. No CVSS, CWE, vendor advisory, or official fixed version is included in the provided sources.

Likely exposure

Organizations running SapphireIMS 5.0 with the portal reachable from the internet or broad internal networks are the likely exposure. The bundle does not support claims about other versions or products.

Exploitation context

Public references and a researcher write-up exist, but CISA KEV status is false and the provided sources do not show active exploitation. Do not assume exploitation in the wild from this bundle alone.

Researcher notes

Evidence is limited to the CVE record and public researcher references. The provided CVE metadata has unknown severity and no affected CPEs. Validate scope carefully and avoid extending impact beyond SapphireIMS 5.0 without additional vendor evidence.

Mitigation direction

  • Identify and inventory all SapphireIMS 5.0 deployments.
  • Restrict portal access to trusted administrative networks or VPNs.
  • Check vendor guidance for supported updates or compensating controls.
  • Review server logs for unexpected portal authentication and diagnostic-function use.
  • Remove public exposure until remediation is confirmed.

Validation and detection

  • Confirm whether SapphireIMS 5.0 is installed in the environment.
  • Verify portal exposure from internet and internal network segments.
  • Review access logs for use of the documented hardcoded account.
  • Review application logs for ping, traceroute, or snmp activity.
  • Confirm installed version and vendor-supported remediation status.
Prepared
Confidence
medium
Sources
4

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-25565 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
3Source links

CVSS and timeline data

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

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.