CVE-2015-10024: A vulnerability classified as critical was found in hoffie larasync

Q: How do I fix CVE-2015-10024?

larasync: upgrade to 2015-01-20. Exact commands for each OS are on this page.

Q: Is CVE-2015-10024 being exploited?

CVE-2015-10024 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2015-10024 affect?

CVE-2015-10024 affects larasync. Severity is medium (CVSS 5.5). A vulnerability classified as critical was found in hoffie larasync. This vulnerability affects unknown code of the file repository/content/file_storage.go. The manipulation leads to path traversal. The name of the patch is 776bad422f4bd493

Q: How urgent is CVE-2015-10024?

Priority 34/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2015-10024 is a medium-severity flaw (CVSS 5.5) affecting larasync. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as critical was found in hoffie larasync. This vulnerability affects unknown code of the file repository/content/file_storage.go. The manipulation leads to path traversal. The name of the patch is 776bad422f4bd4930d09491711246bbeb1be9ba5. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-217612.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-22
Published	2023-01-07
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: larasync project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-01-07 13:15 UTCPublished CVE record published
2026-06-17 00:21 UTCUpdated Record last modified

larasync project larasync UPGRADE

Affected: < 2015-01-20

Fixed in: 2015-01-20

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy larasync || rpm -q larasync || larasync --version

2. UPGRADE to 2015-01-20 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade larasync

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade larasync

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2015-10024?

larasync: upgrade to 2015-01-20. Exact commands for each OS are on this page.

Is CVE-2015-10024 being exploited?

CVE-2015-10024 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2015-10024 affect?

CVE-2015-10024 affects larasync. Severity is medium (CVSS 5.5). A vulnerability classified as critical was found in hoffie larasync. This vulnerability affects unknown code of the file repository/content/file_storage.go. The manipulation leads to path traversal. The name of the patch is 776bad422f4bd493

How urgent is CVE-2015-10024?

Priority 34/100. No elevated risk signals yet.

References

← Back to latest CVEs