other
- Location
rules/transcribe-captions.md:21- Finding
Unrestricted Upload of Local Audio and Filename Metadata to a Third-Party Service
- Content
View full analysis
{ const audioData = fs.readFileSync(audioFilePath).toString('base64'); const filename = audioFilePath.split('/').pop() ?? 'audio.mp3'; const r = await fetch(`${API_BASE}/pilot`, { method: 'POST', headers: { 'Authorization': `Bearer ${SKILLBOSS_API_KEY}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ type: 'stt', inputs: { audio_data: audioData, filename }, }), }); const result = await r.json(); return result.result.text; } ``` ### Technical Analysis The documented implementation accepts a local filesystem path, reads the entire referenced file using the privileges of the executing process, Base64-encodes its contents, and transmits both the contents and basename to `https://api.skillbossai.com/v1/pilot`. Base64 is only a transport encoding and does not provide confidentiality. The resulting request discloses the original audio to a third-party cloud service. Audio can contain confidential conversations, personal data, authentication phrases, customer information, or other regulated content. The filename may independently reveal project names, identities, case numbers, or other sensitive metadata. The example does not include: - Explicit, per-file consent before uploading data. - Validation that the path belongs to an approved media directory. - Protection against paths or symbolic links resolving to unintended files. - Audio MIME type or extension validation. - File-size or upload-volume limits. - A privacy, retention, or data-processing notice for the exter ...[truncated 2499 chars]- Remediation
View remediation
