LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20102: Album Lock getImage path traversal

A vulnerability was found in Album Lock 4.0 and classified as critical. Affected by this issue is some unknown functionality of the file /getImage. The manipulation of the argument filePaht leads to path traversal. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used.

MediumCVSS 4.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Album Lock 4.0 has a path traversal flaw in its getImage function. A local, low-privileged attacker may be able to make the application read or affect files outside the intended image path. Public exploit information exists, but the provided sources do not show active exploitation or a named patch.

Executive priority

Treat this as a moderate-priority legacy application risk. It is not internet-scale based on the sources, but public exploit details and local file-access impact justify prompt inventory and remediation planning where Album Lock 4.0 exists.

Technical view

CVE-2017-20102 is CWE-22 path traversal in Album Lock 4.0 involving the getImage filePaht argument. CVSS 3.1 is 4.4: local vector, low complexity, low privileges, no user interaction, low confidentiality and integrity impact, no availability impact. The affected component is not further described in the sources.

Likely exposure

Exposure appears limited to environments running Album Lock 4.0 where local users or local application contexts can reach the vulnerable getImage functionality. No other versions, products, or hosted deployments are identified in the provided sources.

Exploitation context

The sources state local access is required and public exploit information has been disclosed. CISA KEV status is false in the bundle, and no cited source confirms active exploitation in the wild.

Researcher notes

Evidence is sparse. The CVE identifies Album Lock 4.0, getImage, and filePaht path traversal, but does not name a vendor patch, affected code path details, or broader version range. Avoid assuming remote exposure or active exploitation without additional evidence.

Mitigation direction

  • Inventory systems for Album Lock 4.0 installations.
  • Check vendor or maintainer guidance for updates or removal instructions.
  • Restrict local access to systems running Album Lock.
  • Remove or replace Album Lock 4.0 if no supported fix exists.
  • Monitor application logs for unusual getImage filePaht values.

Validation and detection

  • Confirm whether Album Lock 4.0 is installed or packaged anywhere.
  • Identify whether the getImage endpoint or handler is reachable locally.
  • Review local user and service account access to the application.
  • Check logs for suspicious path traversal patterns without replaying them.
  • Document compensating controls if no patch is available.
Prepared
Confidence
medium
Sources
4

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 · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-20102 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.4 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2017-20102Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
unspecifiedAlbum Lock4.0Listed
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.