Dev.to Security 🔐 Cybersecurity 👁 0 📖 3 min read

iRedAdmin separates global and domain mail administration

iRedAdmin separates global and domain mail administration iRedAdmin is the web administration component for iRedMail. The open-source edition supports global administrators. iRedAdmin-Pro adds domain administrators who

iRedAdmin separates global and domain mail administration

iRedAdmin is the web administration component for iRedMail. The open-source edition supports global administrators. iRedAdmin-Pro adds domain administrators who can manage their own mail domains. The Pro documentation also describes a RESTful API that can manage domains, users, aliases, and administrator assignments.

The separate global and domain roles are useful because mail administration is naturally partitioned by domain. They also create a review problem. A domain administrator who can promote another mail user, change forwarding, reset a password, or alter spam policy has authority over mail flow for that domain. The same person may not be allowed to create a new domain or change the global administrator set.

An internet-facing iRedAdmin page should therefore be mapped to the mail domains it controls. The page title or product fingerprint does not tell you whether the login belongs to a global administrator, a domain administrator, or a self-service user. The account record and the API path do.

Query plan

Use app="iRedAdmin" and title="iRedAdmin" with sub_type=all, page 1, and page size 1. A title match may be a login page for either edition. The application field may vary with the deployment and bundled software. No live measurement is reported because the authorized ZoomEye execution path was rejected by the execution platform in this run.

Record the query role and the response status. If a later approved run finds a candidate, verify domain ownership through DNS and mail records. Do not attempt a login or password reset against an unknown host.

Inventory administrator roles

List global administrators, domain administrators, and self-service users. For each domain admin, confirm the owned domains and whether the account is also a mail user. Review the documented API routes for adding or removing admins. The API can automate the same authority as the web interface, so API access must have a separate credential and audit trail.

Check how administrator accounts are created and recovered. A password reset path that sends mail to an address controlled by the domain administrator can be part of the privilege boundary. Ensure that recovery mail is delivered to a verified mailbox and that the reset token has a short lifetime.

Review self-service settings per domain. Self-service can let users manage forwarding, quarantine, spam policy, and received-mail metadata. Those settings can redirect mail or change what a user can see. Confirm that the domain administrator intentionally enabled each capability and that users cannot change settings reserved for administrators.

Protect the mail control plane

Put the admin interface behind a strong identity path and restrict it to administrative networks. Use multi-factor authentication where the deployment supports it. Separate the global admin from daily mail users and avoid shared credentials. Keep the API behind the same access policy as the web UI.

Monitor admin login failures, password resets, forwarding changes, alias changes, admin promotion, and API calls. Mail-flow changes can be used for business email compromise even when no mailbox content is read. Review SPF, DKIM, DMARC, and relay settings as separate controls.

Investigate a match

Confirm the domain and hosting provider before acting. If the host is yours, review the global admin list and the per-domain admin list. Check recent changes to forwarding and authentication settings. If the host is not yours, preserve evidence without sending mail or attempting account recovery.

iRedAdmin's role separation is valuable, but the roles are not interchangeable. The global administrator controls the service; the domain administrator controls a business mail domain; the self-service user controls personal preferences. Inventory the page, then identify which role can reach it.

References

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.