LiveActive security incident?Get immediate response
CVE Record

CVE-2018-16865: An allocation of memory without limits, that could result in the stack clashing with another memory region,...

An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges. Versions through v240 are vulnerable.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can let an attacker overload systemd-journald, a core Linux logging service, by sending many journal entries. Successful abuse can crash logging or potentially run code with journald privileges. Remote risk is noted only when systemd-journal-remote is in use.

Executive priority

Prioritize remediation on shared Linux servers, externally connected logging paths, and systems with untrusted local users. The issue affects a core service and can impact availability and privilege boundaries.

Technical view

CVE-2018-16865 is a CWE-770 uncontrolled resource allocation flaw in systemd-journald. Versions through v240 can allocate memory without limits, causing a stack clash with another memory region. The CVSS v3.0 score is 7.5, with high attack complexity and low privileges required.

Likely exposure

Exposure is likely on Linux systems using vulnerable systemd versions through v240. Risk is primarily local unless systemd-journal-remote is deployed, which the CVE description identifies as a remote path.

Exploitation context

The bundle includes public exploit-related references, but KEV is false and no cited source here confirms active exploitation. Treat exploit availability as a validation priority, not proof of current attacks.

Researcher notes

Evidence supports vulnerable systemd through v240, local exploitation, and remote exposure only with systemd-journal-remote. The bundle does not provide a universal fixed version, so remediation should be tied to vendor advisories and package backports.

Mitigation direction

  • Apply vendor security updates from the affected Linux distribution or appliance vendor.
  • Prioritize hosts running systemd through v240 or affected vendor builds.
  • Disable or restrict systemd-journal-remote where it is not required.
  • Follow Red Hat, Debian, Ubuntu, Gentoo, NetApp, or Oracle guidance for affected platforms.

Validation and detection

  • Inventory systemd versions and distro package advisory status across Linux assets.
  • Identify whether systemd-journal-remote is installed, enabled, or reachable.
  • Confirm vendor fixed packages are installed on affected systems.
  • Review service health for systemd-journald crashes or repeated restarts.
Prepared
Confidence
high
Sources
8

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-770: 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-16865 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.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/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
17Source 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.0HighCVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.5High
CVSS 3.0 vector shape for CVE-2018-16865Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
The systemd Projectsystemdthrough v240Listed
Weakness

CWE details

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

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.