# CVE-2024-3124: fridgecow smartalarm Backup File androidmanifest.xml backup

> An attacker with physical access can expose backup files due to insecure configuration in the AndroidManifest.xml of the fridgecow smartalarm app.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2024
- **Updated:** 27 Aug 2024
- **Also known as:** GHSA-5jmg-6666-rx6q

## What is CVE-2024-3124?

CVE-2024-3124 is a low-severity vulnerability in fridgecow smartalarm, published on 1 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in fridgecow smartalarm 1.8.1 on Android. This affects an unknown part of the file androidmanifest.xml of the component Backup File Handler. The manipulation leads to exposure of backup file to an unauthorized control sphere. It is possible to launch the attack on the physical device. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-258867.

Weakness: CWE-530 (Exposure of Backup File to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2024-3124?


## How do I fix CVE-2024-3124?

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

## Is CVE-2024-3124 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3124 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3124 and fix it if it is affected.

What it is: CVE-2024-3124 is a low-severity vulnerability in fridgecow smartalarm, published on 1 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3124 exists.

Affected product: fridgecow smartalarm. 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-2024-3124/ (Markdown: https://insights.sbomify.com/CVE-2024-3124/index.md)
```

## Sources

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

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