LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25278: PicaJet FX 2.6.5 Denial of Service via Registration Fields

PicaJet FX 2.6.5 contains a denial of service vulnerability that allows local attackers to crash the application by submitting oversized input to registration fields. Attackers can paste a 6000-byte buffer into the Registration Name and Registration Key fields via the Help menu's Register PicaJet dialog to trigger an application crash.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-25278 affects PicaJet FX 2.6.5, a local desktop application. Oversized text entered into registration fields can crash the application. The known impact is availability loss of the application, not data theft or system takeover. Business urgency is generally limited unless this legacy software supports important workflows.

Executive priority

Treat as a low-to-moderate operational risk. Prioritize remediation if PicaJet FX 2.6.5 is used in business-critical workflows or broadly deployed. Otherwise, handle through normal software hygiene and legacy application cleanup.

Technical view

The vulnerability is a local denial-of-service issue in PicaJet FX 2.6.5 registration handling. Sources describe a crash when oversized input is submitted to registration name/key fields. It is associated with CWE-120 and CVSS 4.0 score 6.9. No remote attack path or privilege escalation is identified in the provided sources.

Likely exposure

Exposure is limited to endpoints where PicaJet FX 2.6.5 is installed and accessible to a local user. Organizations not running this specific version are not indicated as affected by the provided sources.

Exploitation context

The source bundle includes a public Exploit-DB entry, but the CVE is not marked as KEV. Provided evidence supports proof-of-concept availability, not confirmed active exploitation in the wild.

Researcher notes

The available evidence describes a local application crash through oversized registration-field input. Sources do not identify a vendor patch, remote vector, code execution, or active exploitation. CWE-120 suggests unsafe buffer handling, but impact should be treated as denial of service based on cited materials.

Mitigation direction

  • Inventory endpoints for PicaJet FX 2.6.5 installations.
  • Check Picajet or trusted advisories for upgrade, removal, or vendor guidance.
  • Remove the software where it is not business-required.
  • Restrict local access to systems running the affected application.

Validation and detection

  • Confirm whether PicaJet FX 2.6.5 is installed on managed endpoints.
  • Review software inventory records for legacy PicaJet deployments.
  • Check whether users rely on PicaJet for operational workflows.
  • Do not validate by crashing production applications.
Prepared
Confidence
high
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.

cwe · low confidence lookup

CWE-120: 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-2018-25278 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
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

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
6.9CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2018-25278Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PicajetPicaJet FX2.6.5Listed
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.