InfraInbox v0.1 is in development. The self-hosted release and the Cloud beta open on the same day. Sign up for Cloud

This policy is also available in Romanian.

It covers everything InfraInbox publishes or runs: the InfraInbox server and web dashboard, the watcher, the iPhone app, the push relay (push.infrainbox.app), InfraInbox Cloud (dash.infrainbox.app), the infrainbox-push module, the API contracts and SDKs, and the infrainbox.app website.

Report a vulnerability

Please report privately. Don’t open a public issue, discussion or pull request.

Tell us what you found and why it matters, how to reproduce it (or a proof of concept), the product and version or the URL, and whether you know of anyone exploiting it. Write in English or Romanian. If you’d like credit, tell us the name or handle to use.

We don’t run a paid bug bounty. We credit every valid report in the advisory unless you ask us not to.

What to expect

Step When
We confirm we received your report within 3 business days
We tell you whether we accept it, and how severe we rate it (CVSS) within 10 business days
We ship a fix or a mitigation critical: 7 days · high: 30 days · medium: 90 days · low: in a regular release
We update you at least every 14 days until it’s fixed

If a vulnerability is being exploited, we fix or mitigate it first and publish as soon as users can act.

About authorities. EU law requires us to notify Romania’s national CSIRT (DNSC) and ENISA within 24 hours when we learn that a vulnerability in our products is being actively exploited (Cyber Resilience Act, Regulation (EU) 2024/2847, Art. 14). A report alone, without evidence of exploitation, does not trigger this. If it does apply, we share only what the notification needs, and we tell you.

Disclosure

  • We publish an advisory when the fix is released, and credit you.
  • Please keep details private until then, or for 90 days after your report, whichever comes first. We can agree a different date if a fix needs longer, or if users need time to update first.
  • For the server, the watcher and infrainbox-push, advisories are GitHub Security Advisories on the repository, and we request a CVE ID through GitHub for every vulnerability users must act on. For the app, the relay and Cloud, advisories are published at {{ADVISORIES_URL}}. When Cloud or relay users don’t need to do anything, the advisory says so.
  • Every advisory says which versions are affected, how severe it is, and what to do.

How you hear about security fixes

  • GitHub Security Advisories on the repository (use “Watch › Security alerts”).
  • The release feed: {{RELEASE_FEED_URL}}.
  • If you turned on the update check in your server’s setup, a “Security update available” notice in the dashboard. The check sends nothing about your server.
  • Cloud users: an email for anything that affects their account.

Supported versions

Component Gets security fixes How you get them
Server and watcher The newest release, plus the previous minor release for 3 months after a new minor (12 months if the new minor raises a requirement, such as the PostgreSQL version) Upgrade to the newest patch release. It is free and never needs new hardware or a paid component
iPhone app The newest App Store version App Store update. We raise the minimum iOS version only to drop versions Apple no longer patches
Push relay and Cloud Always the running version We patch them; you don’t need to do anything

Support period

We handle security vulnerabilities in every InfraInbox release for at least five years from the date it is published. For a supported release we accept and investigate vulnerability reports, say in every advisory whether that release is affected, and provide the fix through the upgrade path above. Old releases stay downloadable for at least 10 years, marked as unsupported.

Product Release Published End of support
Server 0.1 {{RELEASE_DATE}} {{END_OF_SUPPORT}}
Watcher 0.1 {{RELEASE_DATE}} {{END_OF_SUPPORT}}
iPhone app 1.0 {{RELEASE_DATE}} {{END_OF_SUPPORT}}

Safe harbour

If you research and report in good faith under this policy, we consider your research authorised. We won’t take legal action against you or ask anyone else to, and if someone else does, we’ll say you acted under this policy.

Good faith means you:

  • test only your own self-hosted InfraInbox, or your own Cloud account and workspace;
  • stop as soon as you reach data that isn’t yours, tell us, and don’t keep, share or use it;
  • don’t degrade the service for others: no denial of service, no spam, and no more than 5 requests per second against Cloud or the relay;
  • don’t phish or social-engineer our team or users, and don’t test physical security;
  • give us reasonable time to fix before you disclose.

This can’t bind third parties such as Apple, GitHub or our hosting provider, and it doesn’t override the law. If you’re unsure whether something is allowed, ask us first at contact@innovasoftware.ro.

Out of scope

  • denial-of-service and volumetric attacks;
  • rate-limit or spam issues with no security impact;
  • missing headers or TLS settings without a working attack;
  • self-XSS, and clickjacking on pages with no sensitive action;
  • reports from automated scanners without a proof of concept;
  • attacks that need an already-compromised device, server or account;
  • vulnerabilities in third-party services we use (Apple, Telegram, Slack and so on): report those to them, and tell us if InfraInbox makes it worse.

InfraInbox is made by INNOVA SOFTWARE S.R.L., Romania · CUI 45402130 · Trade Register J30/1284/2021 · legal notice.