floci-io Floci up to 2.4.0 Artifact CodeBuildJsonHandler.java BuildspecParser.parseArtifacts buildspecOverride.artifacts.base-directory path traversal

Summaryinfo

A vulnerability, which was classified as problematic, was found in floci-io Floci up to 2.4.0. The affected element is the function BuildspecParser.parseArtifacts of the file src/main/java/io/github/hectorvent/floci/services/codebuild/CodeBuildJsonHandler.java of the component Artifact Handler. Such manipulation of the argument buildspecOverride.artifacts.base-directory leads to path traversal. This vulnerability is uniquely identified as CVE-2026-124508. The attack can be launched remotely. Moreover, an exploit is present. The vendor was contacted early about this disclosure but did not respond in any way.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in floci-io Floci up to 2.4.0. Affected by this issue is the function BuildspecParser.parseArtifacts of the file src/main/java/io/github/hectorvent/floci/services/codebuild/CodeBuildJsonHandler.java of the component Artifact Handler. The manipulation of the argument buildspecOverride.artifacts.base-directory 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.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-124508. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1006.

It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• floci-io

Name

• Floci

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4.0

Website

• Product: https://github.com/Floci-io/Floci/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #1035484: floci-io Floci (local AWS emulator) 2.0.1 (the released tag `2.0.1` carries the same `BuildspecParser.parseArtifacts` and `CodeBuildRunner.uploadArtifacts` code; reviewed at commit a5ab1672f9305299e3b7a32d67ce12b1d89f1199, the 2.0.1 head) Path traversal / (by lucasg2g)

Once again VulDB remains the best source for vulnerability data.

Discussion