LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51257: An invalid memory write issue in Jasper-Software Jasper v.4.1.1 and before allows a local attacker to execu...

An invalid memory write issue in Jasper-Software Jasper v.4.1.1 and before allows a local attacker to execute arbitrary code.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-51257 is a memory corruption flaw in Jasper-Software Jasper v4.1.1 and earlier. The source record says a local attacker could execute arbitrary code. Business impact is highest where Jasper runs on shared hosts, developer workstations, build systems, or servers that process untrusted files.

Executive priority

Treat as a high-priority patching and exposure-validation item, especially for shared Linux systems and file-processing environments. It is not listed as known exploited in the provided data, so prioritize based on where local users or untrusted processing paths exist.

Technical view

The CVE describes a CWE-119 invalid memory write in Jasper v4.1.1 and before, rated CVSS 7.8. The vector is local, low complexity, low privileges, no user interaction, unchanged scope, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to systems with Jasper v4.1.1 or earlier installed or bundled. The provided affected-product metadata is incomplete, listing vendor and product as n/a, so asset owners should verify installed Jasper packages and embedded dependencies directly.

Exploitation context

The bundle marks CISA KEV as false, and no provided source confirms active exploitation. The CVSS vector indicates exploitation requires local access with low privileges. This is less urgent than a remote unauthenticated flaw, but meaningful on multi-user systems or hosts handling untrusted content.

Researcher notes

Evidence is sparse. The CVE record provides the core vulnerability type, affected version boundary, and CVSS vector, while Fedora advisories indicate downstream packaging attention. The affected CPE data is not populated, so product matching should rely on package inventory and upstream/vendor references.

Mitigation direction

  • Identify systems and applications using Jasper v4.1.1 or earlier.
  • Check upstream GitHub and Fedora advisories for fixed package guidance.
  • Apply vendor-supplied Jasper updates when available.
  • Limit local access on systems where Jasper cannot be promptly updated.
  • Prioritize shared servers, build hosts, and file-processing workflows.

Validation and detection

  • Inventory OS packages and embedded Jasper libraries across managed assets.
  • Compare discovered versions against Jasper v4.1.1 and earlier.
  • Review Fedora advisory applicability for Fedora-managed systems.
  • Confirm updated systems no longer report vulnerable Jasper versions.
  • Check whether any file-processing service invokes Jasper locally.
Prepared
Confidence
medium
Sources
5

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-119: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2023-51257 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
6Source 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.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-51257Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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