LiveActive security incident?Get immediate response
CVE Record

CVE-2015-9019: In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during...

In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function to produce predictable outputs.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

libxslt had a randomness problem: EXSLT math.random could return predictable values because it was not seeded at startup. This matters mainly if an application used that function for security-sensitive decisions. The provided sources do not show active exploitation, a CVSS score, or a named fix.

Executive priority

Treat as targeted cleanup unless business systems use libxslt randomness for security-sensitive values. The available evidence does not support emergency response, but affected legacy dependencies should be inventoried and remediated through normal patch management.

Technical view

CVE-2015-9019 affects libxslt 1.1.29 and earlier per the CVE description. EXSLT math.random was not initialized with a random seed, so generated values could be predictable. Impact depends on whether XSLT transformations used math.random for secrets, identifiers, access decisions, or other trust-sensitive behavior.

Likely exposure

Exposure is likely limited to systems running libxslt 1.1.29 or earlier where XSLT content invokes EXSLT math.random. Risk is higher if output affects tokens, identifiers, authorization logic, or business decisions. The source bundle does not identify specific downstream products or packages.

Exploitation context

The bundle does not indicate CISA KEV listing or active exploitation. Practical abuse would require an application path where an attacker can benefit from predictable math.random output. No exploit technique, public exploitation status, or weaponized details are provided in the sources.

Researcher notes

The core issue is deterministic random output from unseeded EXSLT math.random initialization. Source data lacks CVSS, CWE, exploit status, and explicit remediation details. Validate impact at the application layer because most risk comes from how the function output is consumed.

Mitigation direction

  • Inventory libxslt versions across servers, containers, and embedded runtimes.
  • Check vendor or distribution guidance for fixed or backported libxslt packages.
  • Upgrade libxslt using supported vendor packages where available.
  • Do not use EXSLT math.random for secrets or security decisions.
  • Review XSLT logic for trust-sensitive use of generated random values.

Validation and detection

  • Confirm whether installed libxslt is version 1.1.29 or earlier.
  • Search application XSLT for EXSLT math.random usage.
  • Determine whether random output influences tokens, identifiers, or authorization.
  • Check distro changelogs for backported CVE-2015-9019 fixes.
  • Document affected systems and compensating controls.
Prepared
Confidence
medium
Sources
4

Public sources used

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-9019 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
3Source 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.