obd-auto-doctor

maintainer pingwin840 · 10 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged This PKGBUILD downloads and installs a prebuilt proprietary binary (obdautodoctor) from cdn.obdautodoctor.com over plain HTTP (no TLS), then installs it directly as an executable. The concerns are: (1) the download uses HTTP, not HTTPS, making it trivially interceptable/substitutable by a MITM attacker despite the SHA1 checksums (SHA1 is also weak for integrity guarantees); (2) the binary comes from the vendor's own CDN, which is a plausible official distribution channel for this commercial OBD software, but it is not a well-known, audited package repository; (3) the binary is installed as a setuid-free executable, so no privilege escalation beyond normal user execution. This is a classic medium-risk pattern: a prebuilt closed-source binary from a vendor CDN over HTTP. It is not clearly malicious, but the combination of HTTP transport, SHA1 checksums, and an opaque proprietary binary warrants 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:9 source_i686=("http://cdn.obdautodoctor.com/${pkgname}_${pkgver}_i386.tar.gz")

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 and installs a prebuilt proprietary binary (obdautodoctor) from cdn.obdautodoctor.com over plain HTTP (no TLS), then installs it directly as an executable. The concerns are: (1) the download uses HTTP, not HTTPS, making it trivially interceptable/substitutable by a MITM attacker despite the SHA1 checksums (SHA1 is also weak for integrity guarantees); (2) the binary comes from the vendor's own CDN, which is a plausible official distribution channel for this commercial OBD software, but it is not a well-known, audited package repository; (3) the binary is installed as a setuid-free executable, so no privilege escalation beyond normal user execution. This is a classic medium-risk pattern: a prebuilt closed-source binary from a vendor CDN over HTTP. It is not clearly malicious, but the combination of HTTP transport, SHA1 checksums, and an opaque proprietary binary warrants a medium rating.

PKGBUILD

1 offending line(s) highlighted

      1pkgname=obd-auto-doctor
    
      2pkgver=3.7.4
    
      3pkgrel=1
    
      4pkgdesc="obd scan and diagnostics"
    
      5arch=('i686' 'x86_64')
    
      6url="http://www.obdautodoctor.com/"
    
      7license=('proprietary')
    
      8
    
      9source_i686=("http://cdn.obdautodoctor.com/${pkgname}_${pkgver}_i386.tar.gz")
    
      10source_x86_64=("http://cdn.obdautodoctor.com/${pkgname}_${pkgver}_amd64.tar.gz")
    
      11
    
      12sha1sums_i686=('12a555b5ccddea50318c991f33910b8c2c0e2184')
    
      13sha1sums_x86_64=('43d0c14828a4b08893497dafbb5c2435888ae663')
    
      14
    
      15depends=("qt5-base>=5.9.5")
    
      16optdepends=("bluez: for bluetooth support" "bluez-libs")
    
      17
    
      18[[ "$CARCH" = "i686" ]] && _parch='i386'
    
      19[[ "$CARCH" = "x86_64" ]] && _parch='amd64'
    
      20
    
      21package() {
    
      22	cd "$srcdir/obdautodoctor"
    
      23	install -D -m755 "./obdautodoctor" "${pkgdir}/usr/bin/obdautodoctor"
    
      24	
    
      25	install -D -m644 "./obdautodoctor.desktop" "${pkgdir}/usr/share/applications/obdautodoctor.desktop"
    
      26	install -D -m644 "./obdautodoctor.png" "${pkgdir}/usr/share/pixmaps/obdautodoctor.png"
    
      27
    
      28	install -D -m644 "./license.txt" "${pkgdir}/usr/share/licenses/obdautodoctor/LICENSE"
    
      29}
    
      30

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