openSUSE-SU-2022:0277-1 Test update for SUSE:SLE-15-SP2:Update (security)
Not scored
Published
Check this codebase for openSUSE-SU-2022:0277-1 and fix it if it is affected.
What it is: openSUSE-SU-2022:0277-1 is a vulnerability, published on 1 Feb 2022.
Exploitation: There is no known exploitation of openSUSE-SU-2022:0277-1 in the wild and no public exploit code.
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/openSUSE-SU-2022-0277-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2022-0277-1/index.md)
A security test update for SUSE Linux Enterprise Server 15 SP2, details of the specific vulnerability are not provided.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is openSUSE-SU-2022:0277-1?
openSUSE-SU-2022:0277-1 is a vulnerability, published on 1 Feb 2022.
Official description
This is a security test update for SUSE:SLE-15-SP2:Update
Which versions are affected by openSUSE-SU-2022:0277-1?
How do I fix openSUSE-SU-2022:0277-1?
No fix has been published for openSUSE-SU-2022:0277-1 yet. Limit exposure of the affected software until one is available.
Is openSUSE-SU-2022:0277-1 being exploited?
There is no known exploitation of openSUSE-SU-2022:0277-1 in the wild and no public exploit code.