Filigran OpenCTI 3.3.1 on Linux GET path traversal

Summaryinfo

A vulnerability labeled as critical has been found in Filigran OpenCTI 3.3.1 on Linux. This issue affects some unknown processing of the component GET Handler. Such manipulation leads to path traversal. This vulnerability is documented as CVE-2020-37041. The attack can be executed remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Filigran OpenCTI 3.3.1 on Linux. It has been rated as critical. Affected by this issue is an unknown part of the component GET Handler. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. CVE summarizes:

OpenCTI 3.3.1 is vulnerable to a directory traversal attack via the static/css endpoint. An unauthenticated attacker can read arbitrary files from the filesystem by sending crafted GET requests with path traversal sequences (e.g., '../') in the URL. For example, requesting /static/css//../../../../../../../../etc/passwd returns the contents of /etc/passwd. This vulnerability was discovered by Raif Berkay Dincel and confirmed on Linux Mint and Windows 10.

The weakness was released by Raif Berkay Dincel as 48595. The advisory is shared for download at exploit-db.com. This vulnerability is handled as CVE-2020-37041 since 01/28/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but a public exploit is available. The MITRE ATT&CK project declares the attack technique as T1006.

The exploit is available at exploit-db.com. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Exploit-DB (48595) and EUVD (EUVD-2020-30937). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Filigran

Name

• OpenCTI

Version

• 3.3.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion