LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25160: HTTP::Session2 versions through 1.09 for Perl does not validate the format of user provided session ids, enabling code injection or other impact depending on session backend

HTTP::Session2 versions through 1.09 for Perl does not validate the format of user provided session ids, enabling code injection or other impact depending on session backend. For example, if an application uses memcached for session storage, then it may be possible for a remote attacker to inject memcached commands in the session id value.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's Takemoderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2018-25160 affects Perl applications using HTTP::Session2 through version 1.09. The library did not properly validate user-supplied session IDs. Depending on the session storage backend, an attacker could inject backend commands or cause other unintended behavior. The clearest documented case is memcached-backed session storage.

Executive priority

Treat as a targeted dependency remediation item, not an emergency internet-wide event. Prioritize business-critical Perl applications using HTTP::Session2, especially with memcached sessions. Patch during the next appropriate security maintenance window unless exposure review shows sensitive systems are affected.

Technical view

HTTP::Session2 accepted session IDs without format validation, a CWE-20 input validation flaw. The CVE describes potential command injection when memcached is used as the session backend. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges, no user interaction, with limited confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to Perl applications that use HTTP::Session2 versions through 1.09 and accept session IDs from clients. Risk is higher when the configured session backend interprets session ID content, especially memcached as cited by the CVE.

Exploitation context

No active exploitation is indicated by the provided sources, and the CVE is not listed as KEV. Exploitation depends on application configuration and the session backend. The public description gives memcached command injection as an example but does not establish impact for every backend.

Researcher notes

The source data includes a patch reference and HTTP::Session2 1.10 release notes. The affected-version metadata is less clear than the narrative description, so validate against actual package versions and code usage. Impact is backend-dependent; do not assume universal code execution from the CVE text alone.

Mitigation direction

  • Identify applications using the HTTP-Session2 Perl package.
  • Upgrade HTTP::Session2 to version 1.10 or later where applicable.
  • Review vendor release notes and patch details before production rollout.
  • Prioritize systems using memcached-backed session storage.
  • Add application-side validation for session ID format where feasible.

Validation and detection

  • Inventory Perl dependencies for HTTP-Session2 usage.
  • Confirm deployed HTTP::Session2 versions are not through 1.09.
  • Review application configuration for memcached session storage.
  • Check whether session IDs are accepted from untrusted client input.
  • Verify upgraded deployments use the fixed package version.
Prepared
Confidence
high
Sources
6

Based on public source material and reviewed before publication.

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-20: 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-25160 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A: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
5Source 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.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2018-25160Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
TOKUHIROMHTTP::Session2HTTP-Session2, 0unaffected
Weakness

CWE details

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

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.