{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-1853 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2013-1853 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2013-1853 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2013-1853/ (Markdown: https://insights.sbomify.com/CVE-2013-1853/index.md)","id":"CVE-2013-1853","markdown":"https://insights.sbomify.com/CVE-2013-1853/index.md","name":"CVE-2013-1853","record":{"aliases":["DEBIAN-CVE-2013-1853","GHSA-8j4j-jgp5-w98g","openSUSE-SU-2024:10375-1"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Almanah Diary","requires_auth":"none","summary":"Local attackers can read sensitive diary entries because the application fails to encrypt the database upon closure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"almanah","vendor":"almanah_project"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"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.","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2013-1853","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2013"},"n_packages":1,"n_references":5,"next":{"headline":"Active Record Improper Input Validation","id":"CVE-2013-1854"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["0.11.1-1.15"],"introduced":["0"],"last_affected":[],"package":"almanah","purl":"pkg:rpm/opensuse/almanah\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:10375-1"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2013-1852"},"products":["n/a"],"published":"2014-01-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Local attackers can read sensitive diary entries because the application fails to encrypt the database upon closure.","url":"https://insights.sbomify.com/CVE-2013-1853/"}