cloudme-sync

maintainer orphaned · 2 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged This PKGBUILD downloads a prebuilt binary .deb from cloudme.com (the official vendor domain) and installs it directly without any source build. The binary is executed/installed on the user's system. While cloudme.com is the legitimate upstream vendor, installing prebuilt closed-source binaries from any external host carries inherent supply-chain risk — if the host is compromised or the binary is swapped, the static MD5 checksum (which is cryptographically weak) provides limited protection. Additionally, the checksum logic is broken: the x86_64 md5sums assignment uses a bare statement after a newline following `&&`, meaning the x86_64 checksum may not actually override the i386 one correctly in all bash/makepkg contexts, potentially causing checksum mismatches or silent failures. The package is a legitimate vendor sync client, not piracy or malware, but the combination of a prebuilt binary install, weak MD5 integrity check, and potentially broken architecture-conditional checksum logic justifies a medium rating.

Triggered rules

MEDIUM source=() URL on a non-standard host source_untrusted_domain

One or more source=() URLs point to a host outside the trusted allowlist (github.com, gitlab.com, codeberg.org, pypi.org, …).

PKGBUILD:13 source=("https://www.cloudme.com/downloads/cloudme-sync_${pkgver//_/-}_${_arch}.deb")

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): This PKGBUILD downloads a prebuilt binary .deb from cloudme.com (the official vendor domain) and installs it directly without any source build. The binary is executed/installed on the user's system. While cloudme.com is the legitimate upstream vendor, installing prebuilt closed-source binaries from any external host carries inherent supply-chain risk — if the host is compromised or the binary is swapped, the static MD5 checksum (which is cryptographically weak) provides limited protection. Additionally, the checksum logic is broken: the x86_64 md5sums assignment uses a bare statement after a newline following `&&`, meaning the x86_64 checksum may not actually override the i386 one correctly in all bash/makepkg contexts, potentially causing checksum mismatches or silent failures. The package is a legitimate vendor sync client, not piracy or malware, but the combination of a prebuilt binary install, weak MD5 integrity check, and potentially broken architecture-conditional checksum logic justifies a medium rating.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Yushin Washio <yuwash at yandex dot com>
    
      2 
    
      3pkgname='cloudme-sync'
    
      4pkgver=1.9.8_1.2
    
      5pkgrel=1
    
      6pkgdesc='The CloudMe Sync software for Linux, integrates the CloudMe service with your computer. It enables syncing of multiple folders, sharing and accessing all followed folders.'
    
      7arch=('i686' 'x86_64')
    
      8url='https://www.cloudme.com'
    
      9license=('LGPL')
    
      10depends=('qt5-tools>=5.3.0' 'libgnome-keyring')
    
      11_arch='i386'
    
      12[ "$CARCH" = "x86_64" ] && _arch='amd64'
    
      13source=("https://www.cloudme.com/downloads/cloudme-sync_${pkgver//_/-}_${_arch}.deb")
    
      14 
    
      15md5sums=('3073c8ac70b7dd0d6956b5009c826a57')
    
      16 
    
      17[ "$CARCH" = "x86_64" ] && 
    
      18md5sums=('15e6f13a455e8ba16c5c4ccf20361b1c')
    
      19 
    
      20package() {
    
      21        cd $srcdir
    
      22 
    
      23        ar x *.deb
    
      24        bsdtar xf data.tar.gz -C $pkgdir
    
      25}
    
      26

Scan history

Scanned at (UTC)	Severity	Rules
2026-08-03 00:08:14	MEDIUM	2
2026-08-02 00:16:08	MEDIUM	2
2026-08-01 00:11:18	MEDIUM	2
2026-07-31 00:14:10	MEDIUM	2
2026-07-30 00:17:23	MEDIUM	2
2026-07-29 00:25:53	MEDIUM	2
2026-07-28 00:07:28	MEDIUM	2
2026-07-27 00:24:32	MEDIUM	2
2026-07-26 00:07:32	MEDIUM	2
2026-07-25 00:13:44	MEDIUM	2
2026-07-24 00:02:28	MEDIUM	2
2026-07-23 00:14:47	MEDIUM	2
2026-07-22 00:29:32	MEDIUM	2
2026-07-21 00:24:15	MEDIUM	2
2026-07-20 00:19:49	MEDIUM	2
2026-07-19 00:17:08	MEDIUM	2
2026-07-18 00:14:48	MEDIUM	2
2026-07-17 00:06:16	MEDIUM	2
2026-07-16 00:05:41	MEDIUM	2
2026-07-15 00:09:25	MEDIUM	2