LiveActive security incident?Get immediate response
CVE Record

CVE-2020-23258: An issue found in Jsish v.3.0.11 allows a remote attacker to cause a denial of service via the Jsi_ValueIsN...

An issue found in Jsish v.3.0.11 allows a remote attacker to cause a denial of service via the Jsi_ValueIsNumber function in ./src/jsiValue.c file.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-23258 is a denial-of-service issue in Jsish v3.0.11. A remote, unauthenticated attacker may be able to crash or disrupt software that exposes vulnerable Jsish functionality. The reported impact is availability only; the provided sources do not show data theft, privilege escalation, or active exploitation.

Executive priority

Prioritize remediation for internet-facing or business-critical services using Jsish v3.0.11. The main business risk is service interruption, not confirmed data compromise. If Jsish is absent or not remotely reachable, urgency drops substantially.

Technical view

The CVE describes a flaw in the Jsi_ValueIsNumber function in ./src/jsiValue.c, mapped to CWE-787. CVSS 3.1 is 7.5 with network attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high availability impact.

Likely exposure

Exposure is most likely where Jsish v3.0.11 is embedded in, or directly supports, a network-reachable service. The CVE affected-product metadata is incomplete, so inventory must focus on actual Jsish usage rather than CPE matching.

Exploitation context

The source bundle does not identify public exploit use, and the CVE is not listed as KEV. Treat this as a credible remote crash risk, not as confirmed active exploitation.

Researcher notes

Evidence is sparse. The CVE names Jsish v3.0.11 and a specific function, but affected vendor/product metadata is n/a and no fix version is provided in the bundle. Avoid relying on CPE feeds alone; validate by source, dependency, and runtime inventory.

Mitigation direction

  • Identify whether Jsish v3.0.11 is present in production or shipped software.
  • Check the Jsish project issue and Fossil ticket for vendor-fixed versions or guidance.
  • Remove, upgrade, or isolate vulnerable Jsish deployments where feasible.
  • Restrict network exposure for services that invoke Jsish functionality.
  • Monitor vulnerable services for repeated crashes or abnormal availability failures.

Validation and detection

  • Search asset inventories and build manifests for Jsish v3.0.11.
  • Confirm whether Jsish is reachable through any remote service path.
  • Review application logs for unexplained crashes around Jsish processing.
  • Compare deployed Jsish versions against the referenced project issue and ticket.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
4

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.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-23258 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-23258Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-787

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs