# SUSE-SU-2022:1768-1: Security update for php7

> An attacker can bypass filter_var validation in PHP, potentially leading to security control evasion.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2022

## What is SUSE-SU-2022:1768-1?

SUSE-SU-2022:1768-1 is a vulnerability in php7, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for php7 fixes the following issues:

- Fixed filter_var bypass vulnerability (bsc#1197644).

## Which versions are affected by SUSE-SU-2022:1768-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `php7` | SUSE:Linux Enterprise Module for Package Hub 15 SP3 | All versions | 7.4.6-150200.3.38.2 |
| `php7` | SUSE:Linux Enterprise Module for Web and Scripting 15 SP3 | All versions | 7.4.6-150200.3.38.2 |
| `php7` | openSUSE:Leap 15.3 | All versions | 7.4.6-150200.3.38.2 |
| `php7-test` | openSUSE:Leap 15.3 | All versions | 7.4.6-150200.3.38.2 |
| `php7` | openSUSE:Leap 15.4 | All versions | 7.4.6-150200.3.38.2 |

## How do I fix SUSE-SU-2022:1768-1?

Apply the vendor's patch.

## Is SUSE-SU-2022:1768-1 being exploited?

There is no known exploitation of SUSE-SU-2022:1768-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2022:1768-1 and fix it if it is affected.

What it is: SUSE-SU-2022:1768-1 is a vulnerability in php7, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2022:1768-1 in the wild and no public exploit code.

Affected product: php7. 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/SUSE-SU-2022-1768-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-1768-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2022:1768-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2022-1768-1/
Summaries are generated and may contain mistakes; the official description above is the record.