# openSUSE-SU-2019:1246-1: Security update for blueman

> Local attackers can bypass authentication to modify network configurations via D-Bus due to missing polkit checks in blueman.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Apr 2019

## What is openSUSE-SU-2019:1246-1?

openSUSE-SU-2019:1246-1 is a missing authorization vulnerability in blueman, published on 19 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for blueman fixes the following issues:

The following security issue was addressed:

- Fixed the polkit authorization checks in blueman, which previously allowed
  any user with access to the D-Bus system bus to trigger certain network
  configuration logic in blueman without authentication (boo#1083066).

This update was imported from the openSUSE:Leap:15.0:Update update project.

## Which versions are affected by openSUSE-SU-2019:1246-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `blueman` | SUSE:Package Hub 15 | All versions | 2.0.6-bp150.2.6.1 |

## How do I fix openSUSE-SU-2019:1246-1?

Apply the vendor's patch.

## Is openSUSE-SU-2019:1246-1 being exploited?

There is no known exploitation of openSUSE-SU-2019:1246-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2019:1246-1 and fix it if it is affected.

What it is: openSUSE-SU-2019:1246-1 is a missing authorization vulnerability in blueman, published on 19 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2019:1246-1 in the wild and no public exploit code.

Affected product: blueman. 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/openSUSE-SU-2019-1246-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2019-1246-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2019:1246-1

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