rutoken-pkcs11

maintainer komex · 3 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt .deb binary (a shared library librtpkcs11ecp.so) from download.rutoken.ru, which is the official vendor download server for Rutoken (a Russian hardware security token manufacturer). The library is installed directly into /usr/lib and will be loaded by applications at runtime, making it executed/trusted code. While the host appears to be the legitimate vendor's own distribution server and a sha256sum is provided, the binary is not signed by a distro-trusted key, comes from a vendor-controlled HTTP (not HTTPS) URL, and is a prebuilt native shared library — meaning any compromise of that server or URL would result in arbitrary code execution in any process loading PKCS#11 modules. The HTTP (non-TLS) URL is a notable concern as it allows MITM substitution despite the checksum (the checksum only protects against accidental corruption if the PKGBUILD itself isn't updated). This is a genuine medium-severity supply-chain concern: prebuilt binary from a vendor host over plain HTTP, not a false positive.

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=("http://download.rutoken.ru/Rutoken/PKCS11Lib/${pkgver}/Linux/x64/librtpkcs11ecp_${pkgver}-1_amd64.deb")

MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD downloads a prebuilt .deb binary (a shared library librtpkcs11ecp.so) from download.rutoken.ru, which is the official vendor download server for Rutoken (a Russian hardware security token manufacturer). The library is installed directly into /usr/lib and will be loaded by applications at runtime, making it executed/trusted code. While the host appears to be the legitimate vendor's own distribution server and a sha256sum is provided, the binary is not signed by a distro-trusted key, comes from a vendor-controlled HTTP (not HTTPS) URL, and is a prebuilt native shared library — meaning any compromise of that server or URL would result in arbitrary code execution in any process loading PKCS#11 modules. The HTTP (non-TLS) URL is a notable concern as it allows MITM substitution despite the checksum (the checksum only protects against accidental corruption if the PKGBUILD itself isn't updated). This is a genuine medium-severity supply-chain concern: prebuilt binary from a vendor host over plain HTTP, not a false positive.

PKGBUILD

1 offending line(s) highlighted

      1# Contributor: Andrey Kolchenko <andrey@kolchenko.me>
    
      2
    
      3pkgname=rutoken-pkcs11
    
      4pkgver=2.19.0.0
    
      5pkgrel=1
    
      6pkgdesc='Интерфейс RSALabs PKCS#11'
    
      7arch=('x86_64')
    
      8url='https://www.rutoken.ru/support/download/pkcs/'
    
      9license=('custom:rutoken')
    
      10options=(!strip)
    
      11
    
      12_file='librtpkcs11ecp.so'
    
      13source=("http://download.rutoken.ru/Rutoken/PKCS11Lib/${pkgver}/Linux/x64/librtpkcs11ecp_${pkgver}-1_amd64.deb")
    
      14sha256sums=('6cf9fe1209bc5bcddcc0765171cc6e261a2af43b08e1c3d44f6ff300204934a2')
    
      15
    
      16package() {
    
      17	bsdtar -xf "${srcdir}/data.tar.xz"
    
      18	mkdir -p "${pkgdir}/usr/lib"
    
      19	cp -L "${srcdir}/opt/aktivco/rutokenecp/amd64/librtpkcs11ecp.so" "${pkgdir}/usr/lib"
    
      20	install -Dm644 "${srcdir}/usr/share/doc/rtpkcs11ecp/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
    
      21}
    
      22

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