LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7882: anySign directory traversal vulnerability

Using the parameter of getPFXFolderList function, attackers can see the information of authorization certification and delete the files. It occurs because the parameter contains path traversal characters(ie. '../../../')

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-7882 is a high-severity directory traversal issue in Hancomwith anySign4PC. A remote unauthenticated attacker could use unsafe path input to view authorization certificate information, according to the CVE description. The sources do not confirm active exploitation or provide a specific fixed version.

Executive priority

Prioritize remediation for systems where anySign4PC is deployed and reachable. The main business risk is unauthorized exposure of certificate-related information, with sparse public evidence about exploitation or vendor fixes in the provided sources.

Technical view

The flaw affects anySign4PC versions 1.1.1.0, 1.1.2.6, and 1.1.2.7. The getPFXFolderList function accepts path traversal characters in a parameter, mapped to CWE-24. CVSS 3.1 is 7.5: network exploitable, low complexity, no privileges, no user interaction, high confidentiality impact.

Likely exposure

Exposure is limited to environments running the listed Hancomwith anySign4PC versions. Risk is highest where the vulnerable function is reachable over a network and handles certificate-related file paths or authorization certificate storage.

Exploitation context

The provided sources do not show CISA KEV listing, active exploitation, public exploit details, or observed attacks. They only describe the traversal condition and resulting certificate information exposure. Treat exploitation status as unconfirmed.

Researcher notes

The source bundle contains a CVE description, CVSS vector, CWE-24 classification, affected versions, and a KRCERT reference. It does not provide patch details, exploit maturity, or detailed product deployment context. The CVSS vector lists confidentiality impact only, while the description also mentions file deletion.

Mitigation direction

  • Inventory anySign4PC installations and versions across endpoints and servers.
  • Check Hancomwith or KRCERT guidance for patched versions or vendor workarounds.
  • Upgrade or remove affected versions when vendor-approved remediation is available.
  • Restrict network reachability to any service exposing vulnerable anySign4PC functionality.
  • Review certificate storage permissions and backups for recovery needs.

Validation and detection

  • Confirm whether versions 1.1.1.0, 1.1.2.6, or 1.1.2.7 are installed.
  • Identify systems where getPFXFolderList-related functionality is network reachable.
  • Review logs for suspicious traversal-pattern requests against anySign components.
  • Check for unauthorized access to authorization certificate information.
  • Verify vendor remediation status after applying any update or workaround.
Prepared
Confidence
medium
Sources
3

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-24: 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
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-2020-7882 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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
2Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-7882Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Products and packages named in the record

VendorProductVersion / packageStatus
HancomwithanySign4PC1.1.1.0, 1.1.2.6, 1.1.2.7Listed
Weakness

CWE details

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

CWE-24 · source CWE mapping

Path Traversal: '../filedir'

Path Traversal: '../filedir' represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.