SUSE-SU-2023:1962-1 Security update for indent
Not scored
Published
Check this codebase for SUSE-SU-2023:1962-1 and fix it if it is affected.
What it is: SUSE-SU-2023:1962-1 is a memory corruption vulnerability in indent, published on 24 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of SUSE-SU-2023:1962-1 in the wild and no public exploit code.
Affected product: indent. 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-2023-1962-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2023-1962-1/index.md)
Memory safety flaws in the indent code formatter allow attackers to cause crashes or execute arbitrary code via malicious input.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is SUSE-SU-2023:1962-1?
SUSE-SU-2023:1962-1 is a memory corruption vulnerability in indent, published on 24 Apr 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
This update for indent fixes the following issues:
- Fixed multiple memory safety issues (bsc#1209718).
Which versions are affected by SUSE-SU-2023:1962-1?
Linux distribution packages (15)
indent SUSE:Enterprise Storage 7 | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Enterprise Storage 7.1 | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise Module for Development Tools 15 SP4 | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 2.2.11-150000.3.3.1 |
indent SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 2.2.11-150000.3.3.1 |
indent openSUSE:Leap 15.4 | All versions | 2.2.11-150000.3.3.1 |
How do I fix SUSE-SU-2023:1962-1?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is SUSE-SU-2023:1962-1 being exploited?
There is no known exploitation of SUSE-SU-2023:1962-1 in the wild and no public exploit code.