rwork

MEDIUM

maintainer ernest 1 votes scanned 2026-11-01 00:21:48.120785

View on AUR

Why flagged

This PKGBUILD downloads a prebuilt binary .deb from rwork.crc.com.cn (the vendor's own domain for a Chinese enterprise collaboration app) and installs it directly. The host appears to be the official vendor site matching the package URL, so this is not a random personal host — it is the upstream distribution point. However, the package still installs an unverified prebuilt binary blob: only an MD5 checksum is used (cryptographically weak, no SHA256/b2), and there is no signature verification. The entire /opt tree from the .deb is copied into the system. If the vendor's download server were compromised or the MD5 collided, arbitrary code would execute with user privileges. This is a legitimate medium-risk supply-chain concern: a closed-source binary from a vendor host with only MD5 integrity checking, which is the standard AUR pattern for proprietary apps but still carries real risk compared to source-built packages.

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:9 source=("https://rwork.crc.com.cn/download/Rwork3.0-linux_x64-${pkgver}.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 rwork.crc.com.cn (the vendor's own domain for a Chinese enterprise collaboration app) and installs it directly. The host appears to be the official vendor site matching the package URL, so this is not a random personal host — it is the upstream distribution point. However, the package still installs an unverified prebuilt binary blob: only an MD5 checksum is used (cryptographically weak, no SHA256/b2), and there is no signature verification. The entire /opt tree from the .deb is copied into the system. If the vendor's download server were compromised or the MD5 collided, arbitrary code would execute with user privileges. This is a legitimate medium-risk supply-chain concern: a closed-source binary from a vendor host with only MD5 integrity checking, which is the standard AUR pattern for proprietary apps but still carries real risk compared to source-built packages.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: ernest <307141632@qq.com>
    
      2pkgname=rwork
    
      3pkgdesc="润工作整合即时沟通、云文档、音视频会议、工作台等功能于一体，助力个人与企业开启未来办公新模式！" 
    
      4pkgver=7.32.0
    
      5pkgrel=1
    
      6arch=('x86_64')
    
      7url="https://rwork.crc.com.cn/gxlog/index.html"
    
      8license=('LicenseRef-rwork')
    
      9source=("https://rwork.crc.com.cn/download/Rwork3.0-linux_x64-${pkgver}.deb")
    
      10md5sums=('3ea588611a117c2b6d1ebd4b1d27d266')
    
      11options=('!strip' '!debug')
    
      12DLAGENTS=('https::/usr/bin/curl -A "Mozilla/5.0" -fLC - --retry 3 --retry-delay 3 -o %o %u')
    
      13prepare() {
    
      14    mv "Rwork3.0-linux_x64-${pkgver}.deb" "${pkgver}.deb"
    
      15    ar -x "${pkgver}.deb"
    
      16    mkdir -p "${pkgname}-${pkgver}"
    
      17
    
      18    tar -xf data.tar.xz --directory="${pkgname}-${pkgver}"
    
      19}
    
      20
    
      21package() {
    
      22    cd "$pkgname-$pkgver"
    
      23    cp -r ./ ${pkgdir}/
    
      24    
    
      25    # 安装图标到hicolor主题
    
      26    install -dm755 "${pkgdir}/usr/share/icons/hicolor/scalable/apps"
    
      27    if [ -f "${pkgdir}/opt/crc/rwork/product_logo_256.svg" ]; then
    
      28        cp "${pkgdir}/opt/crc/rwork/product_logo_256.svg" \
    
      29           "${pkgdir}/usr/share/icons/hicolor/scalable/apps/rwork.svg"
    
      30    fi
    
      31    
    
      32    # 修改desktop文件
    
      33    find "${pkgdir}" -name "*.desktop" -type f -exec \
    
      34        sed -i 's/Icon=.*/Icon=rwork/' {} \;
    
      35}
    
      36

Scan history

Scanned at (UTC)	Severity	Rules
2026-11-01 00:21:48	Medium	2
2026-10-31 00:07:41	Medium	2
2026-10-30 00:29:30	Medium	2
2026-10-29 00:13:55	Medium	2
2026-10-28 00:06:54	Medium	2
2026-10-27 00:23:28	Medium	2
2026-10-26 00:12:40	Medium	2
2026-10-25 00:20:48	Medium	2
2026-10-24 00:14:55	Medium	2
2026-10-23 00:02:19	Medium	2
2026-10-22 00:13:10	Medium	2
2026-10-21 00:12:50	Medium	2
2026-10-20 00:10:31	Medium	2
2026-10-19 00:03:55	Medium	2
2026-10-18 00:06:55	Medium	2
2026-10-17 00:21:55	Medium	2
2026-10-16 00:12:47	Medium	2
2026-10-15 00:28:05	Medium	2
2026-10-14 00:06:47	Medium	2
2026-10-13 00:23:45	Medium	2