# CVE-2013-1853: Information disclosure in n/a

> Local attackers can read sensitive diary entries because the application fails to encrypt the database upon closure.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/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:** Yes
- **Published:** 24 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-1853, GHSA-8j4j-jgp5-w98g, openSUSE-SU-2024:10375-1

## What is CVE-2013-1853?

CVE-2013-1853 is a low-severity vulnerability in n/a, published on 24 Jan 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Almanah Diary 0.9.0 and 0.10.0 does not encrypt the database when closed, which allows local users to obtain sensitive information by reading the database.

Weakness: CWE-310

## Which versions are affected by CVE-2013-1853?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `almanah` | openSUSE:Tumbleweed | All versions | 0.11.1-1.15 |

Products: Almanah Project Almanah.

## How do I fix CVE-2013-1853?

Upgrade to a fixed version.

## Is CVE-2013-1853 being exploited?

There is no known exploitation of CVE-2013-1853 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1853 and fix it if it is affected.

What it is: CVE-2013-1853 is a low-severity vulnerability in n/a, published on 24 Jan 2014. 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 CVE-2013-1853 in the wild and no public exploit code.

Affected product: n/a. 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-2013-1853/ (Markdown: https://insights.sbomify.com/CVE-2013-1853/index.md)
```

## Sources

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

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