# CVE-2018-16181: Other in i-FILTER

> Remote attackers can inject HTTP headers to execute scripts or set cookies in i-FILTER web filtering software.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x4fr-465j-hpj9

## What is CVE-2018-16181?

CVE-2018-16181 is a medium-severity vulnerability in Digital Arts Inc. i-FILTER, published on 9 Jan 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

HTTP header injection vulnerability in i-FILTER Ver.9.50R05 and earlier may allow remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks that may result in an arbitrary script injection or setting an arbitrary cookie values via unspecified vectors.

Weakness: CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers)

## Which versions are affected by CVE-2018-16181?

It affects 1 product.


Products: Daj I-Filter.

## How do I fix CVE-2018-16181?

No fix has been published for CVE-2018-16181 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-16181 being exploited?

There is no known exploitation of CVE-2018-16181 in the wild and no public exploit code.

## Other vulnerabilities in Digital Arts Inc. i-FILTER

- [CVE-2018-16180](https://insights.sbomify.com/CVE-2018-16180/): Cross-site scripting in i-FILTER (medium 6.1)
- [CVE-2022-21170](https://insights.sbomify.com/CVE-2022-21170/): Security feature bypass in i-FILTER, i-FILTER Browser & Cloud MultiAgent for Windows, and D-SPA using i-FILTER (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16181 and fix it if it is affected.

What it is: CVE-2018-16181 is a medium-severity vulnerability in Digital Arts Inc. i-FILTER, published on 9 Jan 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-16181 in the wild and no public exploit code.

Affected product: Digital Arts Inc. i-FILTER. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-16181/ (Markdown: https://insights.sbomify.com/CVE-2018-16181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-16181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-16181
- OSV: https://osv.dev/vulnerability/CVE-2018-16181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-16181/
Summaries are generated and may contain mistakes; the official description above is the record.