LiveActive security incident?Get immediate response
CVE Record

CVE-2015-3412: PHP before 5.4.40, 5.5.x before 5.5.24, and 5.6.x before 5.6.8 does not ensure that pathnames lack %00 sequ...

PHP before 5.4.40, 5.5.x before 5.5.24, and 5.6.x before 5.6.8 does not ensure that pathnames lack %00 sequences, which might allow remote attackers to read arbitrary files via crafted input to an application that calls the stream_resolve_include_path function in ext/standard/streamsfuncs.c, as demonstrated by a filename\0.extension attack that bypasses an intended configuration in which client users may read files with only one specific extension.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2015-3412 is a legacy PHP file-handling flaw. A vulnerable PHP application that accepts user-influenced filenames may fail to reject %00 path sequences, letting an attacker bypass intended extension restrictions and read files the application should not expose. Exposure is most likely in unsupported or vendor-maintained legacy PHP 5.4, 5.5, or 5.6 deployments, especially custom applications that resolve include paths from request-controlled filenames. Modern PHP branches are not identified as affected in the source bundle. Treat this as a targeted legacy-platform risk. It is not marked actively exploited, but systems still running affected PHP versions may expose sensitive files through vulnerable application patterns. Prioritize internet-facing and data-sensitive PHP services first. Mitigation focus: Upgrade PHP to 5.4.40, 5.5.24, 5.6.8, or a vendor-fixed package.; Prioritize replacing unsupported PHP 5.x runtimes with supported versions.; Review vendor advisories from Red Hat, Oracle, and PHP for package-specific guidance..

Prepared

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.

cve · low confidence lookup

CVE-2015-3412 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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