rwork

MEDIUM

maintainer ernest 1 votes scanned 2026-09-17 00:27:14.276658

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-09-17 00:27:14	Medium	2
2026-09-16 00:03:17	Medium	2
2026-09-15 00:25:31	Medium	2
2026-09-14 00:27:57	Medium	2
2026-09-13 00:19:54	Medium	2
2026-09-12 00:25:17	Medium	2
2026-09-11 00:19:22	Medium	2
2026-09-10 00:22:44	Medium	2
2026-09-09 00:04:09	Medium	2
2026-09-08 00:18:08	Medium	2
2026-09-07 00:30:15	Medium	2
2026-09-06 00:17:06	Medium	2
2026-09-05 00:16:27	Medium	2
2026-09-04 00:03:13	Medium	2
2026-09-03 00:15:47	Medium	2
2026-09-02 00:02:31	Medium	2
2026-09-01 00:11:19	Medium	2
2026-08-31 00:19:57	Medium	2
2026-08-30 00:04:14	Medium	2
2026-08-29 00:29:17	Medium	2