LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125069: saxman maps-js-icoads exposure of information through directory listing

A vulnerability was found in saxman maps-js-icoads. It has been classified as problematic. Affected is an unknown function. The manipulation leads to exposure of information through directory listing. It is possible to launch the attack remotely. The name of the patch is 34b8b0cce2807b119f4cffda2ac48fc8f427d69a. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-217644.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue can let a remote, authenticated user view directory listings in saxman maps-js-icoads, exposing files or metadata that should not be browsable. The documented impact is limited to confidentiality, with no integrity or availability impact stated.

Executive priority

Treat as a moderate hygiene issue. Prioritize if the project is internet-facing or contains sensitive files, but the supplied evidence does not indicate active exploitation or business-disrupting impact.

Technical view

CVE-2014-125069 is a CWE-548 information exposure through directory listing in saxman maps-js-icoads. The supplied CVSS 3.1 vector is 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. A patch commit is identified, but affected versions and function details are not specified.

Likely exposure

Exposure is likely limited to environments that deploy saxman maps-js-icoads and have not applied commit 34b8b0cce2807b119f4cffda2ac48fc8f427d69a. The source bundle lists versions as n/a and provides no CPEs, so inventory confirmation is required.

Exploitation context

The sources describe remote exploitation with low complexity and low privileges required. The CVE is not listed as KEV in the supplied data, and no cited source here supports active exploitation in the wild.

Researcher notes

Key gaps are affected version range, vulnerable function, and concrete deployment conditions. The PR:L vector matters: validation should model authenticated low-privilege access, not anonymous exposure, unless local configuration broadens access.

Mitigation direction

  • Apply the identified upstream patch commit where saxman maps-js-icoads is used.
  • Disable unintended directory listing in application and hosting configuration.
  • Restrict access to any directories containing non-public files or metadata.
  • Check vendor or repository guidance for any newer maintained remediation.
  • Review logs for unusual access to directory index pages.

Validation and detection

  • Inventory systems and repositories for saxman maps-js-icoads usage.
  • Confirm deployed code includes commit 34b8b0cce2807b119f4cffda2ac48fc8f427d69a or later.
  • Review exposed routes for unintended directory index behavior.
  • Verify authenticated low-privilege users cannot browse sensitive directories.
  • Document version uncertainty because affected versions are not specified.
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 · low confidence lookup

CWE-548: 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-2014-125069 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
4.3 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2014-125069Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
saxmanmaps-js-icoadsn/aListed
Weakness

CWE details

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

CWE-548 · source CWE mapping

Exposure of Information Through Directory Listing

Exposure of Information Through Directory Listing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.