LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25224: PMS 0.42 Stack-Based Buffer Overflow via Configuration File

PMS 0.42 contains a stack-based buffer overflow vulnerability that allows local unauthenticated attackers to execute arbitrary code by supplying malicious values in the configuration file. Attackers can craft configuration files with oversized input that overflows the stack buffer and execute shell commands via return-oriented programming gadgets.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-25224 affects PMS version 0.42. A local unauthenticated attacker who can supply or influence the PMS configuration file may trigger a stack-based buffer overflow and potentially execute code with the privileges of the PMS process.

Executive priority

Prioritize remediation on shared servers, multi-user systems, or environments where configuration files may be generated or modified by untrusted parties. Treat isolated single-user systems as lower urgency but still plan removal or upgrade because public exploit material is referenced.

Technical view

The source bundle describes a stack-based buffer overflow in PMS 0.42 during configuration file handling. Oversized malicious configuration values can overflow a stack buffer, enabling arbitrary code execution according to the CVE description. The listed CVSS v4.0 score is 8.6 High with local attack vector, low complexity, no privileges, and no user interaction. The bundle lists CWE-306, although the vulnerability description itself is for stack-based memory corruption.

Likely exposure

Exposure is most likely on hosts running PMS 0.42 where local users, deployment tooling, shared directories, or other processes can create or modify PMS configuration files. This is not described as remotely network-exploitable in the provided bundle.

Exploitation context

The bundle includes an Exploit-DB reference tagged as exploit, so public exploit material exists. KEV is false, and the provided sources do not state known active exploitation; therefore active exploitation is not asserted.

Researcher notes

Use only the provided source bundle for assessment. Do not claim remote exploitation or active exploitation from the supplied data. Patch status is not established in the bundle, so remediation should be tied to verified vendor guidance rather than an assumed fixed release.

Mitigation direction

  • Check vendor guidance and project resources for an official fix or replacement because the provided bundle does not include patch evidence or a fixed version.
  • Remove or upgrade PMS 0.42 where possible after confirming vendor-supported options.
  • Restrict write access to PMS configuration files and their containing directories to trusted administrators only.
  • Do not run PMS with elevated privileges unless operationally required; use least-privilege service accounts where applicable.
  • Block PMS from processing configuration files supplied by untrusted users or untrusted automation paths.
  • Monitor for unexpected PMS crashes, configuration file changes, or abnormal child process behavior on affected hosts.

Validation and detection

  • Inventory systems for PMS and confirm whether version 0.42 is present.
  • Review PMS configuration file locations and confirm only trusted administrators can modify them.
  • Confirm whether any workflow imports, generates, or accepts PMS configuration files from untrusted local users or external sources.
  • Check vendor/project advisories for fixed versions or deprecation guidance before deciding on upgrade or removal.
  • Review endpoint telemetry for crashes or suspicious activity around PMS execution on affected systems.
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 · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-2018-25224 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
8.6 (4.0)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 4.0 score

8.6High
CVSS 4.0 vector shape for CVE-2018-25224Attack 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:H/VI:H/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
pmsPMS0.42Listed
Weakness

CWE details

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

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.